You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the issue of the command taking 2+ minutes to run is consistent-ish on docker-osuosl-ubuntu2004-ppc64le-1, and started happening on the 26th of June (with the previous run on the 7th taking 14 seconds).
The text was updated successfully, but these errors were encountered:
We have had some disk slowness issues in the past on some of the OSUOSL ppc machines, although I don't think we've hit anything for a while so interesting to see this coming back.
We've had a couple of issues recently flagged by nagios, that align with these failures, ( both times docker filled the disk to 100% capacity ) , and docker was using around 80Gb of disk space for its cache. I'll do some further work, and also increase the thresholds for nagios alerting on this server, so there is more warning to hopefully avoid this issue recurring.
2nd build has completed ok, with similar results so closing, please re-open if this recurrs, and I'll look at it as it happens... I suspect it was probably due to the docker filesystem being full. However Im unable to extend this, as we are at capacity at osuosl.
Please put the system name in the title of this issue.
Link to any log file showing the problem:
Timeout: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-ppc64le-temurin/353/console
First instance of command taking >15 seconds: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-ppc64le-temurin/350/
Last instance of command taking <15 seconds: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-ppc64le-temurin/349/
Looks like the issue of the command taking 2+ minutes to run is consistent-ish on docker-osuosl-ubuntu2004-ppc64le-1, and started happening on the 26th of June (with the previous run on the 7th taking 14 seconds).
The text was updated successfully, but these errors were encountered: