Omit log uploads for env variable defined statuses

[comps]

(This is currently implemented in runcontest, but it would make sense in Contest, especially for new 2025 infra tooling.)

Given an environment variable of ie. CONTEST_NO_LOGS_FOR=pass,warn,info, avoid processing / uploading / recording of additional files (typically logs) when a result is reported with one of the specified statuses, ie.

results.report('pass', ..., logs=[...])

would ignore logs=[...] and treat it as if no logs were passed.

We currently recommend uploading as many logs as possible, even for pass results, to help with debugging / comparing a failing state to as passing state. This may create a data set too big for some infra to handle, hence this option.

We might even have some pass,info,skip default for it, so logs for those are not uploaded (but can be overwritten with CONTEST_NO_LOGS_FOR= empty variable), or something like that.

...

This issue is probably best done during / after any changes for a new 2025 infra tooling.

[comps]

This actually conflicts with #365 and that version is better - a test cannot really tell if it passes or fails mid-run, and we definitely want to upload results mid-run in case the OS freezes, or something like that.

[comps]

Reopening this because I think it is valid for at least some results.

Not for whole-test results (where we want to upload logs as we go), but for fine-grained results where we know the status (pass,fail,etc.) at the same time as we get the logs.

Ie. /per-rule results for each test - based on CONTEST_NO_LOGS_FOR (or whatever it ends up being called), we can avoid an extra rsync of logs from the VM if we don't want to report logs for passing rules/tests.

[matusmarhefka]

Closing, the current way how logs are handled in contest (e.g. tests using add_log()) cannot fulfill this requirement (we don't always know the result status when uploading a log file). Instead, we implemented logs pruning for specified statuses in our productization automation repository.