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

  sio/cirrus-run@5299874

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

  sio/cirrus-run#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 <[email protected]>
Reviewed-by: Ján Tomko <[email protected]>

Author: andreabolognani

.gitlab-ci.yml

@@ -104,7 +104,7 @@ stages:
           -e "s|[@]PYPI_PKGS@|$PYPI_PKGS|g"
       <ci/cirrus/build.yml >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:
     variables:
       - $CIRRUS_GITHUB_REPO