Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failure: python3.pkgs.debugpy #221359

Closed
doronbehar opened this issue Mar 15, 2023 · 6 comments · Fixed by #221772
Closed

Build failure: python3.pkgs.debugpy #221359

doronbehar opened this issue Mar 15, 2023 · 6 comments · Fixed by #221772
Labels
0.kind: build failure A package fails to build

Comments

@doronbehar
Copy link
Contributor

Steps To Reproduce

Steps to reproduce the behavior:

  1. build python3.pkgs.debugpy on latest Nixpkgs master (See recent staging-next merge).

Build log

Tracked upstream: microsoft/debugpy#1241

Notify maintainers

@kira-bruneau

@doronbehar doronbehar added the 0.kind: build failure A package fails to build label Mar 15, 2023
@kira-bruneau
Copy link
Contributor

kira-bruneau commented Mar 15, 2023

Oh nice catch! I'll try a git bisect on the staging-next PR to try to narrow down the cause.

@kira-bruneau
Copy link
Contributor

kira-bruneau commented Mar 16, 2023

Forgot I was running this in the background 😅 - tracked it down to the etils 0.9.0 -> 1.0.0 update:

Bisect Log:
git bisect start 'a86610144f60e8a54f12a75f2ca0ad62e2a5b7fa' 'c34e72182fa2a19a471014b849430b84fdedfb3d'
a86610144f60 bad Merge #219444: staging-next 2023-03-04
c34e72182fa2 good Merge pull request #221295 from fabaff/sqlfluff-bump

git bisect bad e31511712473af7374b9c09609f4b1d7e2980a4b
e31511712473 bad python3Packages.pyglet: 2.0.2.1 -> 2.0.4

git bisect good 87bfed87336d693fcf2de10c9a1861ea4d6ca6ae
87bfed87336d good Merge pull request #218582 from trofi/gnumake-update

git bisect good 75dcf915a22b01b026fae9a2fb3ed2fd7de2d96e
75dcf915a22b good python3Packages.enaml: 0.15.2 -> 0.16.0

git bisect bad 7d5be92d554de6364a6c4adb2742516090fe672c
7d5be92d554d bad python3Packages.lightning-utilities: 0.5.0 -> 0.7.1

git bisect bad 455b6196b403801e52609c20b347a925d013dad3
455b6196b403 bad python3Packages.hupper: 1.10.3 -> 1.11

git bisect bad c4d04911307b7bdaea79801f0fb38b4a7e296c8a
c4d04911307b bad python3Packages.googleapis-common-protos: 1.57.0 -> 1.58.0

git bisect bad e62ffcde66fbc30662e9b7d6844250e4b2d99439
e62ffcde66fb bad python3Packages.flask-admin: 1.6.0 -> 1.6.1

git bisect bad 6e091eb459a15474165f9475f7dfdc90f487cc5b
6e091eb459a1 bad python3Packages.faker: 15.3.4 -> 17.3.0

git bisect bad 22d99610ac1b7c286b83896620add82c409a7520
22d99610ac1b bad python3Packages.ezyrb: 1.3.0.post2212 -> 1.3.0.post2302

git bisect bad a029159e51322101647bb56fb6c53227235fdc13
a029159e5132 bad python3Packages.etils: 0.9.0 -> 1.0.0

git bisect bad a029159e51322101647bb56fb6c53227235fdc13
# first bad commit: [a029159e51322101647bb56fb6c53227235fdc13] python3Packages.etils: 0.9.0 -> 1.0.0

@dotlambda
Copy link
Member

tracked it down to the etils 0.9.0 -> 1.0.0 update

debugpy doesn't depend on etils

@kira-bruneau
Copy link
Contributor

Oh yep, it was probably just a bad automatic bisect then, I'll try manually.

@kira-bruneau
Copy link
Contributor

kira-bruneau commented Mar 16, 2023

Ok, I just ran it again and it just looks like there was just an unrelated error in one of the commits it sampled before:

Bisect Log (12)
git bisect start 'a86610144f60e8a54f12a75f2ca0ad62e2a5b7fa' 'c34e72182fa2a19a471014b849430b84fdedfb3d'
a86610144f60 bad Merge #219444: staging-next 2023-03-04
c34e72182fa2 good Merge pull request #221295 from fabaff/sqlfluff-bump

git bisect bad e31511712473af7374b9c09609f4b1d7e2980a4b
e31511712473 bad python3Packages.pyglet: 2.0.2.1 -> 2.0.4

git bisect good 87bfed87336d693fcf2de10c9a1861ea4d6ca6ae
87bfed87336d good Merge pull request #218582 from trofi/gnumake-update

git bisect bad 75dcf915a22b01b026fae9a2fb3ed2fd7de2d96e
75dcf915a22b bad python3Packages.enaml: 0.15.2 -> 0.16.0

git bisect bad 06d6e8a0ffdeaba1c4614f7407661dc8ec678776
06d6e8a0ffde bad python3Packages.argh: 0.27.2 -> 0.28.1

git bisect bad 8b711e85571b3ccb400e07a7d807fe39f0016b4b
8b711e85571b bad python310Packages.pytest: 7.2.0 -> 7.2.1

git bisect good a74c8d03eab9dc9dd582e939769fab5fb90cd242
a74c8d03eab9 good Merge staging-next into staging

git bisect good d6d83488a774a789a902c3b4f462faa922acf106
d6d83488a774 good Merge pull request #218969 from superherointj/python311Packages.markdown2-2.4.8

git bisect bad ecc65ff29c727b712912826357f7b321cc0a42f5
ecc65ff29c72 bad python310Packages.poetry-core: 1.4.0 -> 1.5.1

git bisect bad eec8bd84c0d849d537740d7d47a9daf8a7951114
eec8bd84c0d8 bad python310Packages.pip: 22.3.1 -> 23.0.1

git bisect bad 451c63214766d3bb8d078620cff4dc74463c5bc8
451c63214766 bad python310Packages.setuptools: 65.0.3 -> 67.4.0

451c63214766d3bb8d078620cff4dc74463c5bc8 is the first bad commit

If this wasn't going to work I was thinking of adding failing inputDrvs as a skip condition. Didn't need to, but it'll be helpful for next time!

@kira-bruneau
Copy link
Contributor

microsoft/debugpy#1230

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: build failure A package fails to build
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants