Repository navigation
deps: cap pytest below 9.2 until pytest-forked handles TestReport._id - #300
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Today's scheduled CI run (https://github.com/sbryngelson/ANEForge/actions/runs/41485001261) failed on unchanged
main(896c494, green on Oct 12/19/26): all 424 off-device tests reportedrunning the test EXITED with status 3, on Linux and all three macOS runners.Cause: pytest 9.2.0 (released Oct 27; last week's green run had 9.1.1) adds a private
TestReport._idholding aNodeIdobject. pytest-forked 1.7.5 (latest) sends each report from the child withmarshal.dumps(rep.__dict__), which can't serializeNodeId, so the child exits 3 and every test fails regardless of its result. A one-linedef test_ok(): assert Truefails the same way underpytest --forked. Reported upstream: pytest-dev/pytest-forked#113.Change:
pytest->pytest<9.2in thedevextra, which every CI job installs, with a comment pointing at the upstream issue. Lift it once pytest-forked ships a fix.Checked locally (Apple M5 Pro, macOS 27.2): pytest 9.2.0 +
--forkedfails; 9.2.0 without forking and 9.1.1 with forking pass. A freshpip install -e ".[dev]"resolves pytest 9.1.1 andpytest -m "not requires_ane"gives 417 passed, 12 skipped. Off-device change.