fedora-ci / general

#223 Timed-out TMT tests fails without an explanation
Closed by mvadkert. Opened by ppisar.

Closed
Reopen Issue

If a TMT tests times out (example https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pipeline/job/master/27193/testReport/(root)/tests/_tests_upstream_tests/), Jenkins shows:

Failed
tests./tests/upstream-tests (from _plans_sanity)
Failing for the past 3 builds (Since Unstable#27191 )
Took 0 ms.
Error Message
Test "/tests/upstream-tests" failed.

and the subsequent test standard output is literally cut somewhere in the middle of the output. It took me some time to found out that it's caused by a too short TMT duration which is 5 minutes by default and my test takes probably longer.

Would it be possible to report the timeout properly somewhere? E.g. "The test exceeded 5 minutes and was terminated."

Thanks for the report. Indeed, we should. Personally feels to me the simplest would be just to print the timeout to the test output.

Actually that the timeout happened is already visible here:

http://artifacts.dev.testing-farm.io/2a915a3f-9bd5-4f1b-8e81-e7b7e77c75bf/work-sanityUUjjT7/plans/sanity/execute/results.yaml

But that means it is hard to see, system running needs to intepret this value to the user.

Taking this to tmt project

https://github.com/psss/tmt/issues/627

HTH: https://github.com/psss/tmt/pull/628

Metadata Update from @mvadkert:
- Issue assigned to mvadkert

Metadata Update from @mvadkert:
- Issue tagged with: tmt

Closing per upstream proposal.

Metadata Update from @mvadkert:
- Issue status updated to: Closed (was: Open)
Metadata

tmt

None
None
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.