-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8354510: Skipped gtest cause test failure #24622
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
Conversation
|
👋 Welcome back aboldtch! A progress list of the required criteria for merging this PR into |
|
@xmas92 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 1 new commit 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 |
robehn
left a comment
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.
Works fine at my end, looks fine, thank you!
|
Thanks for the review |
|
Going to push as commit 76ff978.
Your commit was automatically rebased without conflicts. |
GTEST_SKIPPEDtests count is accounted in gtests run. But when we calculate the number of GTEST errors we takeERROR = RUN - PASSED - FAILED. We need parse and account for the skipped as well. Currently we only account forDISABLEDgtests (which are not counted as run tests).This patch adds support for both
DISABLEDandGTEST_SKIPPEDtests.So with this patch we end up with:
ERROR = RUN - PASSED - FAILED - GTEST_SKIPPEDSKIPPED = GTEST_SKIPPED + GTEST_DISABLEDVerified that this works locally on MacOS and Linux. Currently running through testing and GHA.
The old
matchexpression was problematic with some awk, not sure if there was some other reason it was used, rather than the style used elsewheremaybe set, if unset set=0Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24622/head:pull/24622$ git checkout pull/24622Update a local copy of the PR:
$ git checkout pull/24622$ git pull https://git.openjdk.org/jdk.git pull/24622/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24622View PR using the GUI difftool:
$ git pr show -t 24622Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24622.diff
Using Webrev
Link to Webrev Comment