diff options
author | Chris Evich <cevich@redhat.com> | 2021-01-26 15:05:00 -0500 |
---|---|---|
committer | Chris Evich <cevich@redhat.com> | 2021-02-03 10:44:41 -0500 |
commit | 6a6e86829071d20a7f7fc30d7346c95a6fd3927a (patch) | |
tree | c4151cbfca6421c4d151feb9d7df58cbf504dd02 /contrib/cirrus/pr-should-include-tests.t | |
parent | 4ce8b1281e69b55b6024e87f2dec06638c678f10 (diff) | |
download | podman-6a6e86829071d20a7f7fc30d7346c95a6fd3927a.tar.gz podman-6a6e86829071d20a7f7fc30d7346c95a6fd3927a.tar.bz2 podman-6a6e86829071d20a7f7fc30d7346c95a6fd3927a.zip |
Cirrus: Collect ginkgo node logs artifacts
In rare cases, it's possible for one of the ginkgo processes to "hang".
When this occurs, the main output will contain this message:
``Ginkgo timed out waiting for all parallel nodes to report``
The only way to debug this was to look through concatenated printing
of the ginkgo node logs. This is a tedious and daunting task,
requiring special search knowledge, facing a "wall of text".
Simplify the situation by collecting the node logs separately, as
individual files in a cirrus-artifact. In this way, it's faster to
figure out which test "hung" by examining each log individually. The
log file which does not have a pass/fail summary at the end,
indicates the last test hung (for whatever reason), and includes it's
output (if any).
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'contrib/cirrus/pr-should-include-tests.t')
0 files changed, 0 insertions, 0 deletions