Hi Tom,
as far as I know the timeout in the Fedora CI pipeline is hardcoded to 4 hours https://github.com/CentOS-PaaS-SIG/ci-pipeline/blob/master/config/Dockerfiles/singlehost-test/package-test.sh#L194 and I don't think there is currently a way how this default can be configured. Bruno, can you confirm this?
The duration attribute https://pagure.io/fedora-ci/metadata/blob/master/f/l1/duration.fmf you mention is not implemented yet (see the status field). It is part of the L1 metadata proposal which is still work in progress. On the Flock last week we've just presented https://flock2019.sched.com/event/3bf12a7b3ddda508c2dab6562d1ef533 the first PoC implementing L1 & L2 metadata.
psss...
On Thu, 8 Aug 2019 at 18:35, Tom Stellard tstellar@redhat.com wrote:
Hi,
I've tried to increase the test timeout for the llvm package by adding a duration.fmf file to my tests/ directory.
The file contents look like this:
[tstellar@pkg tests]$ cat duration.fmf
duration: 6h
This did not seem to work for the latest test run:
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-pi...
Is this the correct way to specify a timeout?
-Tom _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org