Repository navigation
Run a failed CPython test once more in the programs podman step - #265
Merged
Merged
Conversation
25 of 37 tasks
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.
The apps job of the 7.4-rc3 programs run (44688230711) failed partly because
test_socketfailed on the rucc kernel and not on the gcc kernel. That set flips from night to night: on 43827513198 the gcc kernel had two failed tests and the rucc kernel one, and on 43725568181 both had two. So a single run of these tests says nothing about the kernel.This runs the suite with
-w, so a test that fails is run once more in verbose mode and only one that fails again is in the failed list compare.py reads. A test the kernel really breaks still fails twice.The other finding of that run, nginx-rps at 0.944 of the gcc kernel, is real and stays. It is tracked in #244.