-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Backport selected bug fixes to 5.10.3 #3838
Comments
@junit-team/junit-5, I've assigned this issue to the |
6 tasks
sbrannen
changed the title
Consider backporting bug fixes to
Consider backporting selected bug fixes to May 31, 2024
5.10.3
5.10.3
Could you also consider back porting #3694? |
marcphilipp
changed the title
Consider backporting selected bug fixes to
Backport selected bug fixes to 5.10.3
Jun 17, 2024
5.10.3
I cherry-picked the relevant commits to the |
🎉 |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
In light of #3820 (comment) and #3820 (comment), and the fact that we have a few additional candidates for backporting, we should consider releasing
5.10.3
with those bug fixes.Todos
TestExecutionListener
cannot fail theTestPlan
#3591@BeforeEach
/@AfterEach
lifecycle methods #3671SuiteLauncherDiscoveryRequestBuilder
#3695NoSuchFileException
in@TempDir
cleanup #3667@EnabledInNativeImage
is not properly supported at the class level #3745NullPointerException
when deserializingTestIdentifier
#3819 (see also PR #3837)ClassOrderer.Random
andMethodOrderer.Random
do not use same default seed #3817The text was updated successfully, but these errors were encountered: