chore(internal/civisibility): reduce civisibility gotesting tests verbosity#3862
Conversation
BenchmarksBenchmark execution time: 2025-08-11 10:48:26 Comparing candidate commit 54fa0b2 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 23 metrics, 1 unstable metrics. |
| fmt.Printf("\n**** [SCENARIO %s IS DONE]\n\n", v) | ||
| if err != nil { | ||
| if exiterr, ok := err.(*exec.ExitError); ok { | ||
| fmt.Printf("\n===========================================\n**** [SCENARIO %s FAILED WITH EXIT CODE: %d]\n", v, exiterr.ExitCode()) |
There was a problem hiding this comment.
Thank you for this! One comment: any reason why we're using fmt.Printf here but log.Debug below? We also have the log.Info function if we need to print regardless of debug mode.
There was a problem hiding this comment.
Yeah, I'm just wanted to make a differentiation between launching the scenarios to test, and the test itself, is more visual than anything. So when I'm testing a scenario all logs within the scenarios uses the internal logger, but here I'm still outside of a testing scenario. As I said, it's only affects visually when I'm debugging.
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
devflow unqueued this merge request: It did not become mergeable within the expected time |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
This PR reduce the logs verbosity in the gotesting tests. It also execute the test in serial mode to reduce the chance of the git shallow lock warning message to happen.
Motivation
When something fails it's hard to read the CI logs due too much logs entries.
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!