-
Notifications
You must be signed in to change notification settings - Fork 94
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
Migrate off JUnit 4 vintage #2495
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Need to confirm same 2079 tests as on develop. |
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
November 15, 2022 00:57
0b48b9b
to
bfdc9b3
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
November 22, 2022 06:38
bfdc9b3
to
90f374b
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
November 29, 2022 11:56
90f374b
to
9f7904e
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
December 6, 2022 15:45
9f7904e
to
8b656ce
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
2 times, most recently
from
December 15, 2022 10:15
dd729a5
to
d7da33c
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
3 times, most recently
from
January 10, 2023 17:44
6d88096
to
e35887e
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
2 times, most recently
from
January 17, 2023 01:43
f6e2311
to
74b7cd1
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
3 times, most recently
from
January 31, 2023 01:55
b703578
to
dbeb38e
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
February 7, 2023 02:20
dbeb38e
to
080588c
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
February 14, 2023 04:55
080588c
to
8c7b4ae
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
February 21, 2023 09:27
8c7b4ae
to
bd04575
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
February 28, 2023 12:14
bd04575
to
43fa412
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
2 times, most recently
from
March 9, 2023 22:22
c44ec1d
to
dcaaf8c
Compare
svc-excavator-bot
force-pushed
the
roomba/junit5
branch
from
March 17, 2023 02:27
dcaaf8c
to
c236e12
Compare
…2601) Apply a large StreamReadConstraints maxStringLength to reduce friction in preparation for jackson 2.15 adoption
[skip ci]
Opt out of canonicalization in Conjure JsonFactories
[skip ci]
SslSocketFactoriesTests checks if Conscrypt is supported
…2609) SslSocketFactories avoids duplicate effort creating TLS components
[skip ci]
Overload client config creation method to allow a TrustContextFactory to be passed as well.
[skip ci]
Merged
Migrate to junit5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR
JUnit 5 excavator #2485 is blocked due to incompatibilities with JUnit 4 vintage usage.
After this PR
==COMMIT_MSG==
Migrate off JUnit 4 vintage
==COMMIT_MSG==
Possible downsides?