build: update to JUnit 5.7.1

[edvbld]

Hi all,

please review this patch that updates JUnit to version 5.7.1 (and JUnit Platform to 1.7.1).

Thanks,
Erik

---

Progress

• Change must not contain extraneous whitespace
• Change must be properly reviewed

Reviewers

• Robin Westberg (@rwestberg - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/skara pull/1087/head:pull/1087
$ git checkout pull/1087

Update a local copy of the PR:
$ git checkout pull/1087
$ git pull https://git.openjdk.java.net/skara pull/1087/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1087

View PR using the GUI difftool:
$ git pr show -t 1087

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/skara/pull/1087.diff

[bridgekeeper]

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

[rwestberg]

Looks good!

[mlbridge]

Webrevs

• 01: Full - Incremental (6d59d0e5)
• 00: Full (6d59d0e)

[openjdk]

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

🔍 One or more changes in this pull request modifies files in areas of the source code that often require two reviewers. Please consider if this is the case for this pull request, and if so, await a second reviewer to approve this pull request before you integrate it.

After integration, the commit message for the final commit will be:

build: update to JUnit 5.7.1

Reviewed-by: rwestberg

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 23 new commits pushed to the master branch:

• 74c9069: build: update to Gradle 6.8.3
• fc91e6d: pr: do not fetch tags for backport command
• 025a0f0: tester: use job id instead of submission id
• 9e66034: pr: update error message for backports
• 99e01cc: 659: Multi-line commands aren't filtered properly
• c33a832: 940: Exception during item execution: has integrated label but no integration comment
• 2234a03: 939: Improve robustness and error reporting on invalid fixVersion
• 3a40804: mlbridge: use nicer link for webrev commits
• 51c3659: pr: fix configuration of forks
• fb56e23: Reviewing help markdown does not work on gitlab
• ... and 13 more: https://git.openjdk.java.net/skara/compare/ffeba1a4f2171dae769b2cddae3fb4b751897a19...master

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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[edvbld]

/integrate

[openjdk]

@edvbld Since your change was applied there have been 32 commits pushed to the master branch:

• 2ff465b: pr: only create backport branch once
• 1137b55: 905: Github UI code markdown can fail to get copied correctly into email
• d9b551d: 769: Replies to e-mail comments on GitHub are threaded incorrectly
• 35dd1da: Backport security level should be inherited from main issue
• f12ee73: 958: Add test cases for known corner cases for synclabel bot
• 4ca65de: 715: Generated email wrongly includes previous unrelated comments
• b404a14: forge: GitLab members endpoint return 404 for non-members
• 87c55b2: 568: RFR mails from the list are not copied to github
• 3d6d56f: 943: remote: GitLab: You can only delete protected branches using the web interface
• 74c9069: build: update to Gradle 6.8.3
• ... and 22 more: https://git.openjdk.java.net/skara/compare/ffeba1a4f2171dae769b2cddae3fb4b751897a19...master

Your commit was automatically rebased without conflicts.

Pushed as commit cd6a10f.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.