We missed this as the tests were not correct (got patch https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/961 for the tests).
Manually testing, I'm getting ~10min delay so far for some runs, and some logs were lost:
tools.automated-toolforge-tests@tools-bastion-13:~$ source ~/venv/bin/activate (venv) tools.automated-toolforge-tests@tools-bastion-13:~$ bats_core_pkg --verbose-run --pretty --timing --recursive --setup-suite-file "/data/project/automated-toolforge-tests/toolforge-deploy/functional-tests/setup_suite.bash" "/data/project/automated-toolforge-tests/toolforge-deploy/functional-tests/tools/" --print-output-on-failure --filter "run a simple scheduled job without filelog, and check the logs" .... 1 test, 1 failure in 198 seconds # then manually waiting tools.automated-toolforge-tests@tools-bastion-13:~$ while ! toolforge jobs logs test-17406; do date; sleep 1; done ERROR: Job 'test-17406' does not have any logs available Wed Sep 10 09:48:59 UTC 2025 ERROR: Job 'test-17406' does not have any logs available Wed Sep 10 09:49:01 UTC 2025 ... ERROR: Job 'test-17406' does not have any logs available Wed Sep 10 09:55:07 UTC 2025 2025-09-10T09:55:01+00:00 [test-17406-29291635-r2qn6] [job] extraword-test-17406 tools.automated-toolforge-tests@tools-bastion-13:~$ toolforge jobs logs test-17406 2025-09-10T09:55:01+00:00 [test-17406-29291635-r2qn6] [job] extraword-test-17406 2025-09-10T09:57:01+00:00 [test-17406-29291637-pkhbv] [job] extraword-test-17406