standard-test-roles

#35 standard-test-beakerlib: custom artefacts defined by tests should be stored, too
Opened by dkutalek. Modified

Open
Close Issue

For investigation of eventual test failures, test authors often use
Beakerlib commands like rlFileSubmit or rlBundleLogs to define specific
testing artefacts to be stored for later investigation.
These are often things like log files, test outputs.
When things brake, simple test output is often not enough to find out why.

Therefore we need to support this in standard-test-beakerlib, too.

Since it is debugging/diagnostic information you are looking for, have you tried setting environment variable TEST_DEBUG=1 before running the tests playbook? Setting this will leave the VM or container running after the playbook has completed so you can log in and investigate failures. See https://fedoraproject.org/wiki/CI/Tests#Testing_an_Atomic_Host and https://fedoraproject.org/wiki/CI/Tests#Testing_a_Container_Image.

Not yet. Could help in some cases, in others not - when failure doesn't happen always.
And of course test author's explicit wish to store given testing artefact isn't satisfied...

Edited by dkutalek

Is it insufficient to have the TEST_ARTIFACTS environment variable as specified in the standard interface docs?

This problem could be solved by adding additional script (to files/ dir for example), which would override rlSubmitFile function of beakerlib (through BEAKERLIB_COMMAND_SUBMIT_LOG variable; the same way beah does it with script /usr/bin/rhts-submit-log).

@jheger Do you recommend that author of /tests uses your proposed approach, or it should be handled by STR?

I think this should be handled by STR.

Commit ccf4f02e relates to this ticket
Metadata
None
None
None
None
None
Related Pull Requests
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.