c576d8bfbb
On the GitLab side we're invoking the Cirrus CI job using the cirrus-run tool which speaks to the Cirrus REST API. Cirrus sometimes tasks 5-10 minutes to actually schedule the task, and thus the execution time of 'cirrus-run' inside GitLab will be slightly longer than the execution time of the Cirrus CI task. Setting the timeout in the GitLab CI job should thus be done in relation to the timeout set for the Cirrus CI job. While Cirrus CI defaults to 60 minutes, it is better to set this explicitly, and make the relationship between the jobs explicit Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Thomas Huth <thuth@redhat.com> Message-Id: <20230912184130.3056054-4-berrange@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20230914155422.426639-7-alex.bennee@linaro.org> |
||
---|---|---|
.. | ||
cirrus | ||
custom-runners | ||
opensbi | ||
base.yml | ||
buildtest-template.yml | ||
buildtest.yml | ||
check-dco.py | ||
check-patch.py | ||
cirrus.yml | ||
container-core.yml | ||
container-cross.yml | ||
container-template.yml | ||
containers.yml | ||
crossbuild-template.yml | ||
crossbuilds.yml | ||
custom-runners.yml | ||
opensbi.yml | ||
qemu-project.yml | ||
stages.yml | ||
static_checks.yml | ||
windows.yml |