ci: test report summary output#2900
Closed
crazy-max wants to merge 2 commits into
Closed
Conversation
crazy-max
force-pushed
the
ci-test-summary
branch
from
36e2280 to
0d1286c
Compare
crazy-max
force-pushed
the
ci-test-summary
branch
3 times, most recently
from
a517d86 to
dc1335b
Compare
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
ci-test-summary
branch
from
dc1335b to
be5831f
Compare
Member
Author
|
As discussed with @tonistiigi, resulting summary might not be useful in the current state. What would be interesting is to capture popular failure points over time to catch performance regressions. Without dedicated nodes it looks difficult to catch atm. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Aggregate data from JSON reports of Go tests using gotestsum and adds a step for unit and integration tests that will render the output as markdown and create a GitHub summary in our workflow using teststat:
Also some useful stats about slow tests:
Was also thinking using tparse to have a better overview: https://github.com/crazy-max/buildkit/actions/runs/2453700879#summary-6772166685
But output is quite huge.
@thaJeztah Maybe gotestsum could also generate a markdown summary output so we don't need extra tools. WDYT?