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
treewide: simplify some dependency cycles #43627
Conversation
propagatedBuildInputs = [ attrs coverage ] ++ lib.optional (!isPy3k) [ enum34 ]; | ||
|
||
checkInputs = [ pytest pytest_xdist flaky mock ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unnecessary change
unnecessary change
It's necessary for satisfying my OCD of grouping related things together.
|
@GrahamcOfBorg eval |
Success on x86_64-linux (full log) Attempted: glib, libffi Partial log (click to expand)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/cc @vcunat @domenkozar
glib-tested
was a part of release.nix
until it was removed in c21f936, probably due to mysterious Nix failures on Hydra. Its build has not been failing since then.
pkgs/top-level/all-packages.nix
Outdated
doCheck = true; | ||
libffi = libffi.override { doCheck = true; }; | ||
# dependency cycle | ||
libffi = libffi.override { doCheck = false; }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this override necessary? I can instantiate glib
without it.
Success on aarch64-linux (full log) Attempted: glib, libffi Partial log (click to expand)
|
Is this override necessary? I can instantiate `glib` without it.
Oops, right, that's because `glib` has `doCheck` set to `true` by default in my branch and I have not upstreamed those patches yet.
I tried to split stuff into bite-sized pieces, but failed in this instance.
Then, the logical way to proceed is to close this PR and to postpone this discussion till I get those patches ready then.
|
9bd0085
to
acbee90
Compare
On the second though, nothing prevents me from removing only that part from here too. Updated.
The glib things will go into a separate PR.
|
Success on aarch64-linux (full log) Attempted: libffi Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: libffi Partial log (click to expand)
|
@GrahamcOfBorg build python2Packages.pytest python2Packages.hypothesis |
Success on x86_64-linux (full log) Attempted: python2Packages.pytest, python2Packages.hypothesis Partial log (click to expand)
|
Ping. Anything holding this now?
|
Success on aarch64-linux (full log) Attempted: python2Packages.pytest, python2Packages.hypothesis Partial log (click to expand)
|
FYI. This broke the darwin stdenv. |
Ok. Unless there is an alternative fix available we can just do |
Yeah, I'm testing to see if there are any other problems. |
Yet another followup to #39464.