-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
ALL
-
Execution Team 2024-08-05, Execution Team 2024-08-19, Execution Team 2024-09-02, Execution Team 2024-09-16
When spawning a host for some failing evergreen tasks (specifically noticed for this burn_in task and this burn_in task) the core dumps generated from the test don't appear on the spawned host though the binaries do. This error appears in the host's logs:
++ ls '/data/mci/artifacts-*/mongo-coredumps-*.tgz' + COREDUMP_ARCHIVE= + [[ -n '' ]] + COREDUMP_ARCHIVE_TARGET=./ + for filename in /data/mci/artifacts-*/dump_*.core.gz ++ readlink -f '/data/mci/artifacts-*/dump_*.core.gz' + COREDUMP_ARCHIVE= ++ basename basename: missing operand Try 'basename --help' for more information. + COREDUMP_ARCHIVE_BASENAME= + mv ./ mv: missing destination file operand after './' Try 'mv --help' for more information. /data/mci/source-patch-436_mongodb-mongo-master ~/debug ~/debug Waiting for background processes to complete. + gunzip .// gzip: .// is a directory -- ignored ++ ls './/dump*' + [[ -z '' ]] + archive_fail coredump + echo 'Error: archive [coredump] not found.' Error: archive [coredump] not found.