Skip to content

Properly work with test failures caused during beforeAll phase#3194

Merged
elharo merged 1 commit intoapache:masterfrom
Frawless:before-all-flakes
Oct 8, 2025
Merged

Properly work with test failures caused during beforeAll phase#3194
elharo merged 1 commit intoapache:masterfrom
Frawless:before-all-flakes

Conversation

@Frawless
Copy link
Contributor

@Frawless Frawless commented Sep 29, 2025

Closes #2622
Closes #2950

The PR change the reporter logic to determine if failures in @BeforeAll phase were resolved during re-runs which means these are just flakes or if the failures are really errors.

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean install to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean install).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

Signed-off-by: Jakub Stejskal <xstejs24@gmail.com>
@elharo elharo merged commit 4a47a1c into apache:master Oct 8, 2025
26 checks passed
@elharo elharo added the bug Something isn't working label Oct 8, 2025
@github-actions
Copy link

github-actions bot commented Oct 8, 2025

@elharo The PR can't be associated to a milestone, because there are multiple open milestones. Please add the text "branch: master" to the description to the milestone where this PR belongs to.

@olamy
Copy link
Member

olamy commented Oct 8, 2025

This need an IT and was expected to get one
Why did you merge this??

@elharo
Copy link
Contributor

elharo commented Oct 8, 2025

There was no comment here saying anything like that, or a request for changes. It looked good and important to me, so I merged it. You can still add an integration test if you want one, but my judgment remains that we're better off with this PR than without it.

@Frawless
Copy link
Contributor Author

Frawless commented Oct 8, 2025

I will open followup PR with IT hopefully today, just doing some last testing of changes I did.

Frawless added a commit to Frawless/maven-surefire that referenced this pull request Oct 29, 2025
apache#3194)"

This reverts commit 4a47a1c.

Signed-off-by: Jakub Stejskal <xstejs24@gmail.com>
Frawless added a commit to Frawless/maven-surefire that referenced this pull request Nov 13, 2025
apache#3194)"

This reverts commit 4a47a1c.

Signed-off-by: Jakub Stejskal <xstejs24@gmail.com>
Tibor17 pushed a commit that referenced this pull request Nov 14, 2025
#3194)"

This reverts commit 4a47a1c.

Signed-off-by: Jakub Stejskal <xstejs24@gmail.com>
Frawless added a commit to Frawless/maven-surefire that referenced this pull request Nov 14, 2025
apache#3194)"

This reverts commit 4a47a1c.

Signed-off-by: Jakub Stejskal <xstejs24@gmail.com>
olamy pushed a commit that referenced this pull request Nov 15, 2025
#3194)"

This reverts commit 4a47a1c.

Signed-off-by: Jakub Stejskal <xstejs24@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

3 participants