-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8323994: gtest runner repeats test name for every single gtest assertion #17489
Conversation
👋 Welcome back szaldana! A progress list of the required criteria for merging this PR into |
@SoniaZaldana To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
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.
Good. Thanks for fixing.
/label hotspot-runtime |
@SoniaZaldana 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 287 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@tstuefe, @lmesnik) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@tstuefe |
Webrevs
|
/integrate |
@SoniaZaldana |
Let's wait for a second review (need two in hotspot territory) snd the obligatory 24 hrs. /reviewer 2 |
@tstuefe Only the author (@SoniaZaldana) is allowed to issue the |
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.
Please remove space and update copyrights. Otherwise fix looks good.
@@ -57,7 +57,10 @@ public GTestResultParser(Path file) { | |||
testCase = xmlReader.getAttributeValue("", "name"); | |||
break; | |||
case "failure": | |||
failedTests.add(testSuite + "::" + testCase); | |||
String failedStr = testSuite + "::" + testCase; | |||
if (! failedTests.contains(failedStr)) { |
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.
Please remove space between '! and failed..'.
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.
Thanks @lmesnik! I pushed the changes.
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.
Still good. Ship it.
@SoniaZaldana you need to newly slash integrate. |
/integrate |
@SoniaZaldana |
/sponsor |
Going to push as commit 1aae980.
Your commit was automatically rebased without conflicts. |
@tstuefe @SoniaZaldana Pushed as commit 1aae980. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
If GTest fails multiple times within the same test (for example when EXPECT or ASSERT are used in a subroutine),
GTestResultParser
repeats the failing test multiple times in its report.Please refer to the existing issue for an example.
We only need to see the failing test reported once, so this patch fixes that.
Let me know your thoughts.
Cheers,
Sonia
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17489/head:pull/17489
$ git checkout pull/17489
Update a local copy of the PR:
$ git checkout pull/17489
$ git pull https://git.openjdk.org/jdk.git pull/17489/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17489
View PR using the GUI difftool:
$ git pr show -t 17489
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17489.diff
Webrev
Link to Webrev Comment