The job definitions recently got a second "variables:" section by
accident and thus are failing now if one tries to run them. Merge
the two sections into one again to fix the issue.
And while we're at it, bump the timeout here (70 minutes are currently
not enough for the aarch64 job). The jobs are marked as manual anyway,
so if the user starts them, they want to see their result for sure and
then it's annoying if the job timeouts too early.
Fixes: e312d1fdbb ("gitlab: convert build/container jobs to .base_job_template")
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
I wonder whether we should remove the build-cfi-aarch64 job instead.
When I tried to run it during the past months, it was always failing
for me. This time, I tried to bump the timeout while I was at it,
and it takes longer than 80 minutes here to finish - so I asume
nobody ever ran this successfully in the last months... Is anybody
using this job at all? I think if we want to have CFI coverage here,
it should get replaced by a custom runner job that runs on a more
beefy machine... (the ppc64-s390x job is fine by the way, it often
only runs a little bit longer than 60 minutes - I still bumped the
timeout here, too, just to be on the safe side)