-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use assertRegex instead of deprecated assertRegexpMatches v2 #7576
Open
janvrany
wants to merge
2
commits into
eclipse-omr:master
Choose a base branch
from
janvrany:pr/jitbuilder-fix-deprecated-method-in-apigen-tests
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Use assertRegex instead of deprecated assertRegexpMatches v2 #7576
janvrany
wants to merge
2
commits into
eclipse-omr:master
from
janvrany:pr/jitbuilder-fix-deprecated-method-in-apigen-tests
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
`assertRegexpMatches` was renamed to `assertRegex` in Python 3.2 and has been removed entirely in Python 3.10. Our CI systems should all have at least Python 3.2. Rename uses to `assertRegex`. Fixes: eclipse-omr#7181 Signed-off-by: Daryl Maier <maier@ca.ibm.com>
Previous commit renamed `assertRegexpMatches` to `assertRegex` as the former has been removed in Python 3.12. However, at the time of writing, not all CI build agents have been upgraded to Python >= 3.2. At the same time, some agents have Python 3.12 and cannot be easily downgraded (e.g., RISC-V). This commit provides a compatibility with Python < 3.2 by implementing `assertRegex` by means of `assertRegexpMatches` if `assertRegex` is not available. This way, JitBuilder API gen tests should pass everywhere. Once all CI nodes are upgraded, this commit can be reverted.
jenkins build all |
Both Linux RISC-V and OSX AArch64 failures seems unrelated - some CI hiccups? |
jenkins build riscv |
3 similar comments
jenkins build riscv |
jenkins build riscv |
jenkins build riscv |
jenkins build amac |
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 is another stab on using
assertRegex
instead ofassertRegexpMatches
(previous attempts: #7279, #7496)What prompted me to get back to this again is recent work on reviving RISC-V build using Eclipse-provided native build agents (#7530, #7556).
This PR contains @0xdaryl's original commit changing
assertRegexpMatches
toassertRegex
. The second commit monkey-patches class to provide the latter when not available (i.e., on Python < 3.2).