We seem to be experiencing intermittent issues where a step for a particular container is not producing output. This causes the container to abort after the preset time, subsequent steps that save artifacts and analysis show that the job is indeed running. Examining the other containers running in parallel show no issues.
The script in question smoke.sh first runs an IF to test a condition, then a binary IF which regardless of condition runs an echo command, this should always cause output at the beginning. Looking at the referenced link above, you can see no output for step
Smoke Tests in container 5, but other containers have valid output.
This has occurred for us across different jobs/steps and cannot seem to be isolated to something controllable on our side of the fence.