Fix flaky tests #60
Merged
Fix flaky tests #60
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: StefMa <[email protected]>
Signed-off-by: StefMa <[email protected]>
ov7a
approved these changes
Jan 25, 2024
|
Thank you for your contribution! |
Signed-off-by: Stefan M. <[email protected]>
ov7a
approved these changes
Jan 25, 2024
|
LGTM, Thank you! |
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.
fixes #58
Changes:
can pick the right packageonly for the major version[a-z0-9]{32}(as hash).Its better, not perfect (yet) 😅
There is the java 22 test that will fail as soon as it is available/released.
The test were added in #55
Not sure if its required to test against version 22.. Maybe we want to test against version 100 (or so)?
Just to test that we don't get anything in case we request an version that is not available?!
Le me know if I should change this or keep it for whatever reasons 🙃