On Mon, Aug 12, 2019 at 3:41 PM Dominik Perpeet <dperpeet(a)redhat.com> wrote:
What would be the impact of just increasing the hardcoded max duration to 6 hours?
Just some tests when they hung or the system hungs it will take 2 more
hours to have the results. It will also take 2 more hours to have the
resources free. If that's fine I see no problem to raise the timeout.
We just need a new issue requesting it on
https://pagure.io/fedora-ci/general/
>
> -Dominik
>
>
> On Mon, Aug 12, 2019 at 2:54 PM Bruno Goncalves <bgoncalv(a)redhat.com> wrote:
>>
>> On Mon, Aug 12, 2019 at 2:39 PM Petr Šplíchal <psplicha(a)redhat.com> wrote:
>> >
>> > Hi Tom,
>> >
>> > as far as I know the timeout in the Fedora CI pipeline is hardcoded to 4
hours and I don't think there is currently a way how this default can be configured.
Bruno, can you confirm this?
>> >
>>
>> Correct, this is hardcoded in the pipeline, we currently don't have a
>> way to dynamically change it. We didn't expect any test playbook to
>> take longer than 4hrs to execute. Would be possible to split the test
>> in separate tests*.yml playbook? As each tests*.yml would run in a
>> clean environment and each one would have 4hrs as timeout.
>>
>> Bruno
>>
>> > The duration attribute 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 the first PoC implementing L1 & L2 metadata.
>> >
>> > psss...
>> >
>> > On Thu, 8 Aug 2019 at 18:35, Tom Stellard <tstellar(a)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...
>> >>
>> >>
>> >> Is this the correct way to specify a timeout?
>> >>
>> >> -Tom
>> >> _______________________________________________
>> >> CI mailing list -- ci(a)lists.fedoraproject.org
>> >> To unsubscribe send an email to ci-leave(a)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
>> _______________________________________________
>> CI mailing list -- ci(a)lists.fedoraproject.org
>> To unsubscribe send an email to ci-leave(a)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
>
> _______________________________________________
> CI mailing list -- ci(a)lists.fedoraproject.org
> To unsubscribe send an email to ci-leave(a)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