-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Simplify test build output normalization #77172
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
Simplify test build output normalization #77172
Conversation
cd51e16 to
e564c9c
Compare
|
Pinging @elastic/es-delivery (Team:Delivery) |
| import org.gradle.testkit.runner.TaskOutcome; | ||
| import org.gradle.testkit.runner.UnexpectedBuildFailure; | ||
| import org.gradle.testkit.runner.UnexpectedBuildSuccess; | ||
| import org.jetbrains.annotations.Nullable; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We seem to use both this import and javax.annotation.Nullable. Do we have a "correct" one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed both. In general I avoid org.jetbrains.annotations.Nullable for sure. Sneaks in sometimes via code generators. Seems like I have to tweak my local setup
mark-vieira
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
💔 Backport failed
To backport manually run |
* Simplify test build output normalization
always normalise output of gradle runner