Issues on benchmark ci

[rjbou]

These days, I've seen several buggy behaviour with benchmarks on opam:

• Failing with no log
• Docker issues, see here & here
• No bench job associated to a PR

[shakthimaan]

Thanks for raising an issue. A recent system upgrade is causing these behaviors.. We are currently troubleshooting the Docker and benchmark failures, and we will keep you posted on any further updates.

[avsm]

How's this troubleshooting going?

[punchagan]

• Failing with no log

I've not yet had a chance to look into this in detail, but I've created an issue for it that we will track on the current-bench repo.

• Docker issues, see here & here

The docker issues were because of the disk running out of inodes and we have mitigated the issue by switching to a larger disk, though we haven't yet figured out the reason for the docker overlay2 layers not being garbage collected, even when they seem to be no longer used.

• No bench job associated to a PR

Some of the missed PRs were because the service was unstable due to the disk space (inode) issues. This should be resolved now.

[tmattio]

My understanding is that the issue has been addressed. Closing now, but please re-open if that's not the case.