Closed gasche closed 4 months ago
Thanks for the report; looks like ocaml-benching is missing an org in the deployment (like https://github.com/tarides/ocaml-benching), causing the corrupt Dockerfile. /cc @punchagan @art-w @samoht
Thanks for the report; looks like ocaml-benching is missing an org in the deployment (like https://github.com/tarides/ocaml-benching), causing the corrupt Dockerfile. /cc @punchagan @art-w @samoht
Thanks for the report. It was a buggy configuration that caused the issue. I've fixed the configuration and restarted the service. We can close the issue once a new build is available.
Thanks for looking at the issue! As of today, the last build reported on https://bench.ci.dev/ocaml/ocaml/branch/trunk is a failed build from January 29th. I don't know if it just takes a few days for the machine to pick up new trunk commits, or if there should have been rebuilds by now that did not happen.
The builds are configured to happen only on Mondays. But, from memory I thought for a failed latest build the new build should get triggered the next time a webhook notification is fired. I'll look into this, and try to get a new run started.
We now have the benchmark runs data.
Thanks a lot @punchagan!
https://bench.ci.dev/ocaml/ocaml/branch/trunk
currently shows a build failure. It looks like the last working build happened in November 2023.
The build log of the last failure ends as follows: