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

[Backports stable/1.0] Fix flaky test analysis with integration tests #7434

Merged
4 commits merged into from
Jul 2, 2021

Conversation

npepinpe
Copy link
Member

@npepinpe npepinpe commented Jul 2, 2021

Description

This PR backports #7413 to stable/1.0. The merge conflicts were all in the parent/pom.xml and related to versions which have been updated on develop, but not here. I've kept the original versions to resolve them.

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

  • The changes are backwards compatibility with previous versions
  • If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/0.25) to the PR, in case that fails you need to create backports manually.

Testing:

  • There are unit/integration tests that verify all acceptance criterias of the issue
  • New tests are written to ensure backwards compatibility with further versions
  • The behavior is tested manually
  • The change has been verified by a QA run
  • The impact of the changes is verified by a benchmark

Documentation:

  • The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
  • New content is added to the release announcement

Modifies the flaky test extractor profile such that it's only activated
manually. The reasoning here is that this is only used for CI and not
for local development, so it's fine to have to manually enable it.

This also fixes the usage of the plugin, which was not working with
failsafe since it was not looking in the right directory. The profile
now has a property which it uses to specify whether to look into
surefire-reports or failsafe-reports. It was done this way because
normally the plugin expects a full directory, but here we don't know the
project's directory, just that in there it should look up
failsafe/surefire reports. So instead of specifying it on all projects,
we just have to set one property before running maven.

One downside is the plugin has to run in the post-integration-test
phase, so we now unnecessarily package the application even for unit
tests.

(cherry picked from commit 7d8c54f)
Dependency and plugin resolve when going offline produce a lot of noise
which we don't care about. We can switch it to silent, and
errors/warnings will still be logged correctly. You can always turn it
back to noisy if you need to debug things.

(cherry picked from commit 4cb9033)
@npepinpe npepinpe force-pushed the backport-7413-to-stable/1.0 branch from 8a9e26a to c0e07ef Compare July 2, 2021 11:15
@npepinpe npepinpe requested a review from pihme July 2, 2021 11:16
Copy link
Contributor

@pihme pihme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bors r+

@ghost
Copy link

ghost commented Jul 2, 2021

Build succeeded:

@ghost ghost merged commit 0dd3123 into stable/1.0 Jul 2, 2021
@ghost ghost deleted the backport-7413-to-stable/1.0 branch July 2, 2021 11:57
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants