-
-
Notifications
You must be signed in to change notification settings - Fork 679
Closed
Description
We run some fairly big and verbose test suites on github actions (.e.g: https://github.com/kumahq/kuma/actions/runs/8245083767/job/22550558820).
We could use ::group::
to group the stdout output for example which would make things much easier to read see for docs: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#grouping-log-lines
This would make the output a lot easier to read.
From a quick look at the code it should likely be somewhere there:
ginkgo/reporters/default_reporter.go
Lines 284 to 306 in 977bc6f
//Emit Stdout/Stderr Output | |
if showSeparateStdSection { | |
r.emitBlock("\n") | |
r.emitBlock(r.fi(1, "{{gray}}Captured StdOut/StdErr Output >>{{/}}")) | |
r.emitBlock(r.fi(1, "%s", report.CapturedStdOutErr)) | |
r.emitBlock(r.fi(1, "{{gray}}<< Captured StdOut/StdErr Output{{/}}")) | |
} | |
if showSeparateVisibilityAlwaysReportsSection { | |
r.emitBlock("\n") | |
r.emitBlock(r.fi(1, "{{gray}}Report Entries >>{{/}}")) | |
for _, entry := range report.ReportEntries.WithVisibility(types.ReportEntryVisibilityAlways) { | |
r.emitReportEntry(1, entry) | |
} | |
r.emitBlock(r.fi(1, "{{gray}}<< Report Entries{{/}}")) | |
} | |
if showTimeline { | |
r.emitBlock("\n") | |
r.emitBlock(r.fi(1, "{{gray}}Timeline >>{{/}}")) | |
r.emitTimeline(1, report, timeline) | |
r.emitBlock(r.fi(1, "{{gray}}<< Timeline{{/}}")) | |
} |
It could either be a command line flag: --github-output
or detect it using en env var like: GITHUB_ACTIONS=true
.
koct9i
Metadata
Metadata
Assignees
Labels
No labels