Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

SoniaZaldana
Copy link
Member

@SoniaZaldana SoniaZaldana commented Jan 18, 2024

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

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8323994: gtest runner repeats test name for every single gtest assertion (Bug - P4)

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

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 18, 2024

👋 Welcome back szaldana! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jan 18, 2024

@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
  • build
  • client
  • compiler
  • core-libs
  • graal
  • hotspot
  • hotspot-compiler
  • hotspot-gc
  • hotspot-jfr
  • hotspot-runtime
  • i18n
  • ide-support
  • javadoc
  • jdk
  • jmx
  • kulla
  • net
  • nio
  • security
  • serviceability
  • shenandoah

@SoniaZaldana SoniaZaldana marked this pull request as ready for review January 24, 2024 14:11
@openjdk openjdk bot added the rfr Pull request is ready for review label Jan 24, 2024
Copy link
Member

@tstuefe tstuefe left a 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.

@tstuefe
Copy link
Member

tstuefe commented Jan 24, 2024

/label hotspot-runtime

@openjdk
Copy link

openjdk bot commented Jan 24, 2024

@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:

8323994: gtest runner repeats test name for every single gtest assertion

Reviewed-by: stuefe, lmesnik

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 master branch:

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 /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added ready Pull request is ready to be integrated hotspot-runtime hotspot-runtime-dev@openjdk.org labels Jan 24, 2024
@openjdk
Copy link

openjdk bot commented Jan 24, 2024

@tstuefe
The hotspot-runtime label was successfully added.

@mlbridge
Copy link

mlbridge bot commented Jan 24, 2024

Webrevs

@SoniaZaldana
Copy link
Member Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jan 24, 2024
@openjdk
Copy link

openjdk bot commented Jan 24, 2024

@SoniaZaldana
Your change (at version 279fb7d) is now ready to be sponsored by a Committer.

@tstuefe
Copy link
Member

tstuefe commented Jan 24, 2024

Let's wait for a second review (need two in hotspot territory) snd the obligatory 24 hrs.

/reviewer 2

@openjdk
Copy link

openjdk bot commented Jan 24, 2024

@tstuefe Only the author (@SoniaZaldana) is allowed to issue the reviewer command.

Copy link
Member

@lmesnik lmesnik left a 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)) {
Copy link
Member

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..'.

Copy link
Member Author

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.

@openjdk openjdk bot removed the sponsor Pull request is ready to be sponsored label Jan 25, 2024
Copy link
Member

@tstuefe tstuefe left a 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.

@tstuefe
Copy link
Member

tstuefe commented Feb 6, 2024

@SoniaZaldana you need to newly slash integrate.

@SoniaZaldana
Copy link
Member Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Feb 12, 2024
@openjdk
Copy link

openjdk bot commented Feb 12, 2024

@SoniaZaldana
Your change (at version 765f826) is now ready to be sponsored by a Committer.

@tstuefe
Copy link
Member

tstuefe commented Feb 15, 2024

/sponsor

@openjdk
Copy link

openjdk bot commented Feb 15, 2024

Going to push as commit 1aae980.
Since your change was applied there have been 319 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Feb 15, 2024
@openjdk openjdk bot closed this Feb 15, 2024
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Feb 15, 2024
@openjdk openjdk bot removed rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Feb 15, 2024
@openjdk
Copy link

openjdk bot commented Feb 15, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot-runtime hotspot-runtime-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants