-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Display phase name in stash dump of a test failure. #5223
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
Gradle Check (Jenkins) Run Completed with:
|
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 14, 2022 13:10
edf11df
to
5d5f485
Compare
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 15, 2022 02:12
5d5f485
to
c412a11
Compare
Gradle Check (Jenkins) Run Completed with:
|
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 15, 2022 18:49
c412a11
to
641293b
Compare
Gradle Check (Jenkins) Run Completed with:
|
I'm just waiting for those S3 YAML tests to fail :) too lazy to write a long loop |
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 16, 2022 12:57
641293b
to
07ba39a
Compare
Gradle Check (Jenkins) Run Completed with:
|
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 16, 2022 18:49
07ba39a
to
87e4605
Compare
Gradle Check (Jenkins) Run Completed with:
|
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 17, 2022 14:33
87e4605
to
626c053
Compare
Gradle Check (Jenkins) Run Completed with:
|
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 17, 2022 17:54
626c053
to
11e97c2
Compare
Gradle Check (Jenkins) Run Completed with:
|
Signed-off-by: dblock <[email protected]>
dblock
force-pushed
the
phase-in-test-failure
branch
from
November 17, 2022 22:36
11e97c2
to
4915f57
Compare
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## main #5223 +/- ##
============================================
+ Coverage 71.02% 71.04% +0.01%
+ Complexity 58161 58156 -5
============================================
Files 4704 4704
Lines 277401 277401
Branches 40166 40166
============================================
+ Hits 197025 197071 +46
+ Misses 64204 64154 -50
- Partials 16172 16176 +4
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
@reta I believe you've looked at the flaky yaml/REST tests, this might be useful. I'll close it for now. |
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.
Signed-off-by: dblock [email protected]
Description
Looking at failures in #5219 it's not immediately obvious whether the failure is in setup/execution/teardown. You can deduce it from the above lines, but it doesn't cost much to display it inline with the dump.
Leaving this as draft, should trigger enough gradle failures to see it be useful/not.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.