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
add pythonPackages.outcome, pythonPackages.trio #40191
Conversation
sha256 = "0cqwakzigw0602dxlb7c1882jwr8hn5nrxk1l8iwlmzc9whh48wn"; | ||
}; | ||
|
||
propogatedBuildInputs = [ attrs ]; |
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.
propagatedBuildInputs
ec2f07a
to
ab62319
Compare
OK, that's fixed now. The next issue is that the "outcome" package has a test dependency on "trio", and "trio" has a normal dependency on "trio". Is there any way to resolve this without disabling tests? Maybe run test it in a joint environment? I also filed an issue upstream about it: python-trio/outcome#12 Furthermore, even if I disable tests for outcome, the trio tests also then fail with a cryptic message about pytest.config. (in next comment) |
Other than that, it works:
(don't merge yet though) |
|
||
checkInputs = [ pytest ]; | ||
propagatedBuildInputs = [ attrs ]; | ||
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.
add a comment why
The error about
|
sha256 = "0ib1x47knlad9pljb64ywfiv6m3dfrqqjwka6j1b73hixmszb5h4"; | ||
}; | ||
|
||
checkInputs = [ pytest pyopenssl trustme ]; |
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.
You're sure the last two are only needed for testing?
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.
Yes, they're only listed in test-requirements.txt, not in setup.py; and I don't believe there's any place that the trio library would use them.
@GrahamcOfBorg build python3.pkgs.trio |
Failure on x86_64-linux (full log) Attempted: python3.pkgs.trio Partial log (click to expand)
|
OK, with some changes and importing another test dependency, the tests for trio are mostly running. Just a few failing tests. Now the obstacle is some apparent sandbox issue. It looks like maybe /etc/services isn't present in the sandbox? Can we suggest a workaround upstream?
|
I'd say just disable the failing tests. |
Failure on aarch64-linux (full log) Attempted: python3.pkgs.trio Partial log (click to expand)
|
@GrahamcOfBorg build python3.pkgs.trio |
Success on x86_64-linux (full log) Attempted: python3.pkgs.trio Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: python3.pkgs.trio Partial log (click to expand)
|
This pull request doesn't yet build. I have a separate pull request
for the first two packages in this series, since they build fine.
The problem starts at the "outcome" package. It fails with:
Even though attrs is in its propagatedBuildInputs... any ideas?