ci: Temporarily enable verbose mode for cirrus-run

We've hit issues with GitLab CI jobs reporting a failure despite
the corresponding Cirrus CI job finishing successfully: this is
apparently caused by the underlying VM being rescheduled.

A workaround for this issue has been implemented as of

  5299874bbb

which will be included in the upcoming 0.3.0 release; however, in
order to validate that this workaround is effective it would be
useful to have more data.

Based on the conversation in

  https://github.com/sio/cirrus-run/issues/4

enabling verbose mode allows to collect this data while not having
any impact on performance, so let's enable it temporarily and then
disable it again once cirrus-run 0.3.0 is out.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
Andrea Bolognani 2020-08-04 12:00:41 +02:00
parent d8f13661e0
commit 9b5622d31f
1 changed files with 1 additions and 1 deletions

View File

@ -104,7 +104,7 @@ stages:
-e "s|[@]PYPI_PKGS@|$PYPI_PKGS|g" -e "s|[@]PYPI_PKGS@|$PYPI_PKGS|g"
<ci/cirrus/build.yml >ci/cirrus/$NAME.yml <ci/cirrus/build.yml >ci/cirrus/$NAME.yml
- cat ci/cirrus/$NAME.yml - cat ci/cirrus/$NAME.yml
- cirrus-run --show-build-log always ci/cirrus/$NAME.yml - cirrus-run -v --show-build-log always ci/cirrus/$NAME.yml
only: only:
variables: variables:
- $CIRRUS_GITHUB_REPO - $CIRRUS_GITHUB_REPO