python3Packages.einops: fixed tests#152291
python3Packages.einops: fixed tests#152291yl3dy wants to merge 1 commit intoNixOS:masterfrom yl3dy:einops_fix
Conversation
|
Result of 2 packages built:
|
There was a problem hiding this comment.
I'm not sure you really have to bother tidying up after yourself or setting HOME back to its previous setting. Many packages set HOME in the checkPhase and I'm not sure I've ever seen any bother setting it back.
There was a problem hiding this comment.
Also, completely replaced checkPhases could do with runHook preCheck and runHook postCheck and the beginning and end respectively.
There was a problem hiding this comment.
I've been wondering about that, why is that needed? Does python add something to those phases, or is it for easier overriding?
There was a problem hiding this comment.
The hooks? AFAIK It's purely for the convenience of people who may need to override elements of the package and e.g. set their own extra preCheck, expecting it to work rather than being ignored.
There was a problem hiding this comment.
Many packages set HOME in the checkPhase and I'm not sure I've ever seen any bother setting it back.
It was more of a precaution, so removed that.
Also, completely replaced checkPhases could do with runHook preCheck and runHook postCheck and the beginning and end respectively.
Added, thanks a lot for the suggestion!
Tests now utilize a separate HOME created via `mktemp`: using just TMPDIR makes `test_layers::test_torch_layer` sometimes fail.
|
@GrahamcOfBorg build python3Packages.einops |
|
The tests seem to hang on test_torch_layer on ofborg and in my local tests. It seems like all tests are passing within 3m on the upstream github actions CI. |
What system do you use? I tried building via |
|
@yl3dy I was testing on non-nixos x86_64-linux running on an i7-3770K with sandboxing enabled. |
|
I just tried running nixpkgs-review on this PR and it's still hung up right after I believe it should be reproducible running on any of the m5 instances (at least). @yl3dy What kind of CPU are you running OOC? Anything else unusual about your setup? |
|
I'm running Core i7-12700K at NixOS 21.11 (stable channel), no dGPU. Running on CPU might be the most unusual, compared to non-Nix testing. |
|
Closing in favor of #154115 |
Motivation for this change
Fix occasionally stuck tests, see #152049.
Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)nixos/doc/manual/md-to-db.shto update generated release notes