This may be due to build environment (hardware), race conditions, or perhaps the exact image used to run the test.

But it is less reliable than in other environments.

Suggested next steps:

Reproduce in docker (locally) the steps to run the ATH, to reproduce the problem
try alternative docker images
Look at error in the ATH that stop it from existing, or picking up false failures (if they are false).