-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
8315415: OutputAnalyzer.shouldMatchByLine() fails in some cases #15753
Conversation
👋 Welcome back lmesnik! A progress list of the required criteria for merging this PR into |
/cc hotspot |
@lmesnik |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems reasonable. But it doesn't seem to fix the issue that was reported in the bug report. Was that test subsequently modified to ensure the line did not happen to contain regex pattern meta-characters?
The test doesn't use this API. As I understand Calvin find this problem while writing tests, and decided to just to write it other way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay - thanks.
@lmesnik This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 5 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 7b1e2bf.
Your commit was automatically rebased without conflicts. |
OutputAnalyzer.shouldMatchByLine(from, to, pattern)
treat from and to parameters as patterns and not lines. So it might fail to compile them or work not as expected in some cases.
I grepped the usage of shouldMatchByLine and stdoutShouldMatchByLine and found that in most cases from/to are set to some regex patterns. So I just updated the names of variables and documentation to explicitly say that from/to are patterns.
See bugs for details. Tested with tier1 (mostly for validation scripts since no code changes.)
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15753/head:pull/15753
$ git checkout pull/15753
Update a local copy of the PR:
$ git checkout pull/15753
$ git pull https://git.openjdk.org/jdk.git pull/15753/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15753
View PR using the GUI difftool:
$ git pr show -t 15753
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15753.diff
Webrev
Link to Webrev Comment