[WFCORE-5805] HostControllerBootOperationsTestCase fails intermittent… #5032
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
…ly when Security Manager is enabled Jira issue: https://issues.redhat.com/browse/WFCORE-5805
github-actions
bot
added
the
deps-ok
|
Thanks, @yersan |
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.
…ly when Security Manager is enabled
Jira issue: https://issues.redhat.com/browse/WFCORE-5805
This PR follow-ups on #4961.
It adds 40 seconds more to the overall test to ensure we are not hitting failures when CI is pretty busy :(. Ideally, we should be able to unlock the Byte man rule by issuing
signalWakewhen the test condition is satisfied, but it is really difficult to find a condition that can be used to trigger the awake by using the same identifier ($this). So I'm trying this with the hope that this additional time is acceptable. It is a workaround though, it won't ensure we will never going to pass the limit that ensures the test can be run, but for the last failures, it looks enough.