[env_op_images] Reduce POST-RUN console output#4051
Conversation
sdatko
force-pushed
the
reduce-logs
branch
4 times, most recently
from
f656f0a to
d4ab6ff
Compare
|
nice improvement @sdatko ! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evallesp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
FINALLY READY FOR REVIEW |
nemarjan
left a comment
nemarjan
left a comment
There was a problem hiding this comment.
LGTM overall -- the 80% reduction in job-output.txt is a big win, and I like that all the data is still preserved as artifacts. Just left a small suggestions inline, nothing blocking.
This commit suppress verbose console output from Kubernetes API queries and CRI-O log collection tasks to reduce POST-RUN phase output by ~80% in Zuul jobs. The suppressed data that were previously visible in `job-output.txt` were actually redundant and already collected in ci-framework-data/ artifacts anyway as: - `operator_images.yaml` - `crio_logs/*` Keeping `job-output.txt` smaller reduces impact on the web browser when opening Zuul build logs. For debugging purposes logging can be re-enabled by setting the `cifmw_nolog: false` variable. Changes: - Add `no_log` to 4 tasks `env_op_images` role. - Reworked the CRI-O log collection tasks. Impact: - 75% reduction in console output (~60k → ~15k lines) - 90% smaller file size (~20 MB → ~2 MB) - All data still preserved for subsequent tasks + dumped as artifacts Assisted-by: Claude Sonnet 4.5 Signed-off-by: Szymon Datko <sdatko@redhat.com>
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 25m 45s |
|
recheck |
5 participants
This commit suppress verbose console output from Kubernetes API
queries and CRI-O log collection tasks to reduce POST-RUN phase
output by ~80% in Zuul jobs.
The suppressed data that were previously visible in
job-output.txtwere actually redundant and already collected in ci-framework-data/
artifacts anyway as:
operator_images.yamlcrio_logs/*Keeping
job-output.txtsmaller reduces impact on the web browserwhen opening Zuul build logs.
For debugging purposes logging can be re-enabled by setting
the
cifmw_nolog: falsevariable.Changes:
no_logto 4 tasksenv_op_imagesrole.Impact:
Assisted-by: Claude Sonnet 4.5