mirror of
https://github.com/containers/podman
synced 2024-10-20 17:23:30 +00:00
6a6e868290
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> |
||
---|---|---|
.. | ||
99-do-not-use-google-subnets.conflist | ||
add_second_partition.sh | ||
cirrus_yaml_test.py | ||
cron-fail_addrs.csv | ||
ext_svc_check.sh | ||
lib.sh | ||
logcollector.sh | ||
logformatter | ||
logformatter.t | ||
pr-should-include-tests | ||
pr-should-include-tests.t | ||
required_host_ports.txt | ||
runner.sh | ||
setup_environment.sh | ||
shellcheck.sh | ||
swagger_stack_trace.png | ||
timestamp.awk |