Relax C910V qemu utest timeout#5900
Draft
mpwaser wants to merge 1 commit into
Draft
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.
Summary
This relaxes the C910V QEMU timeout for
openblas_utest.The timeout showed up while checking #5899, but #5899 only changed CMake/CTest registration. The failing C910V job uses the make build and runs
openblas_utestdirectly under QEMU.Details
The failing job repeatedly reaches:
and then restarts the whole unit-test binary with short timeout windows.
This keeps the existing retry defaults, but lets callers override them. Only the observed slow binary gets a larger budget:
openblas_utest_extkeeps the default retry behavior because the observed timeout happens before it runs.Scope
Limited to
.github/workflows/c910v.yml.Validation
Checked the relevant Actions history:
29003486034, job86079876651: timed out atopenblas_utestfork:safety.developrun29007407697, job86082261750: same timeout pattern.developrun28967557753, job85954497464: same test reached timeout retries before eventually passing.