The archive_dist_test task on enterprise-amazon2023-arm64 (and potentially other variants) fails with a "no such file or directory" error when attempting to archive .gcno files. The failure occurs because the archive script uses the pattern ./*/.gcno which recursively traverses the entire workspace, including Bazel's temporary directories (tmp/bazel-output-root/*/sandbox/_moved_trash_dir/). This creates a race condition: while the archive script is traversing these directories, Bazel's background garbage collection process is simultaneously moving and deleting files in the trash directory, causing file-not-found errors. The .gcno pattern is unnecessary for non-coverage build variants (which don't generate .gcno files) and redundant for coverage variants (which handle .gcno files separately through
code_coverage_data_process.py
). Removing the ./*/.gcno pattern from archive_dist_test eliminates the race condition without any functional impact.