Fix GHA check failures 2025-02-19 #627
Merged
Conversation
This file contains 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
Signed-off-by: Roscoe A. Bartlett <[email protected]>
The GHA container updated the version of codespell being usesd. I can't install codespell 2.2.6 on my local RHEL8 machine so I can't test this locally :-( Signed-off-by: Roscoe A. Bartlett <[email protected]>
…esting These tests are timing out for some reason at 1 minute in GHA testing. They don't timeout when run locally. It is almost impossible to reproduce failures in GHA testing. Signed-off-by: Roscoe A. Bartlett <[email protected]>
bartlettroscoe
added
type: bug
component: testing
bartlettroscoe
changed the title
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.
This PR should fix the lingering GHA check failures that popped up recently. This should allow the nightly GHA builds to start working again and should allow PRs like #624 to pass tests and merge.
In particular, the GHA container upgraded the version of codespell it was using (to codespell 2.2.6-1) which trigged a bunch of more misspelled words (which is good). Also, the COVERAGE tests started timing out at 1 minute on testing day 2025-01-09. Not clear why that happened but don't have time to see why that is the case.
See commit messages for more details.