| commit | 998f3347223234eeb2f47235eaa222cf0ee7f8ca | |
| author | Daniel P. Berrangé <berrange@redhat.com> | |
| Mon, 25 Jul 2022 14:05:09 +0000 (25 15:05 +0100) | ||
| committer | Alex Bennée <alex.bennee@linaro.org> | |
| Fri, 29 Jul 2022 08:48:01 +0000 (29 09:48 +0100) | ||
| tree | dabfc33afea09cfc778ee27fbba1af18b5d7ecce | treesnapshot (tar.gz zip) |
| parent | feb6cb936906ad049bdc77ef176b1d402e341c29 | commitdiff |
gitlab: show testlog.txt contents when cirrus/custom-runner jobs fail
When tests fail meson just displays a summary and tells you to look at
the testlog.txt file for details. The native jobs on shared runners
publish testlog.txt as an artifact. For the Cirrus jobs and custom
runner jobs this is not currently possible. The best we can do is cat
the log contents on failure, to give maintainers a fighting chance
of diagnosing the problem.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20220722130431.2319019-3-berrange@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20220725140520.515340-3-alex.bennee@linaro.org>
When tests fail meson just displays a summary and tells you to look at
the testlog.txt file for details. The native jobs on shared runners
publish testlog.txt as an artifact. For the Cirrus jobs and custom
runner jobs this is not currently possible. The best we can do is cat
the log contents on failure, to give maintainers a fighting chance
of diagnosing the problem.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20220722130431.2319019-3-berrange@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20220725140520.515340-3-alex.bennee@linaro.org>