functional2 test_toml_invalid_argument_types fails due to PATH shenanigans (on macOS?) #964
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#964
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
on
3de996f5
:Basically it seems like the pytest being used recursively is not the same pytest as the one that's being used not-recursively. This is probably because the pytest being invoked not-recursively is putting a bad pytest into the head of PATH.
cc @helle.
repro, seems to happen on aarch64-linux too:
can you provide the return value of
shutil.which("pytest")
within a python shell (base level)also, how did it pass ci then?
i am guessing it is some bullshit related to whether it's pytest from a python env vs pytest from a pile of build inputs. but not sure! let me get you that.
compare:
This is an identical issue upstream as https://github.com/NixOS/nixpkgs/issues/248978
lol, okay, this just fixes it. i wonder why we default to breaking python programs.
This issue was mentioned on Gerrit on the following CLs: