Description of problem:

The CNCF test scenario timed out when the periodic job ran as a presubmit for a PR that changed the test scenarios. The timeout message is buried deep in the log from the CNCF scenario, and that scenario reports no junit output when it times out.

Version-Release number of selected component (if applicable):

4.16

How reproducible:

Flakey?

Steps to Reproduce:

1.
2.
3.

Actual results:

The run.log for the CNCF scenario says "Tests running for 1h. Timing out", but that message is mixed in with so much other `bash -x` output it was hard to find. Even figuring out that it was the CNCF scenario that failed required studying the build-log.txt file where `scenario.sh run` is executed and noticing that the scenario exited with status 2.

Expected results:

A junit result showing that the scenario failed, ideally with the timeout message included.

Additional info:

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_microshift/2952/pull-ci-openshift-microshift-main-metal-periodic-test/1759975202717962240/artifacts/metal-periodic-test/openshift-microshift-e2e-metal-tests/build-log.txt

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_microshift/2952/pull-ci-openshift-microshift-main-metal-periodic-test/1759975202717962240/artifacts/metal-periodic-test/openshift-microshift-e2e-metal-tests/artifacts/scenario-info/el92-src@cncf-conformance/run.log