We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lint-fmt
On https://ocaml.ci.dev/github/ocaml-multicore/picos/commit/9392f253fa5741352e552072335958d210334d0b/variant/%28lint-fmt%29
We are failing with
rm: cannot remove '/home/opam/.opam/4.08/.opam-switch/sources/astring.0.8.5/test/total.ml': Permission denied rm: cannot remove '/home/opam/.opam/4.08/.opam-switch/sources/astring.0.8.5/test/testing.mli': Permission denied rm: cannot remove '/home/opam/.opam/4.08/.opam-switch/sources/astring.0.8.5/test/testing.ml': Permission denied
Reruning the job is reproducing
I've run the steps on the base docker container, and it's working as expected. So it doesn't seem to be an issue with the base image.
The text was updated successfully, but these errors were encountered:
I wonder if it is worker specific? I've moved the job to another worker. The queue is heavily backlogged so it'll be tomorrow before we see a result.
Sorry, something went wrong.
It is not worker specific. Happening now on x86-bm-c9.sw.ocaml.org :/ seems the file perms have been borked some how?
https://ocaml.ci.dev/github/ocurrent/ocaml-ci/commit/dd5494c1332e687b8ae0cf44e756ccaa26b87b47/variant/%28lint-fmt%29
This is fixed by 48ba2f5
The cause was an error I introduced in #937 by mixing up the order of the docker actions. Sorry for the trouble and noise there.
No branches or pull requests
Context
On https://ocaml.ci.dev/github/ocaml-multicore/picos/commit/9392f253fa5741352e552072335958d210334d0b/variant/%28lint-fmt%29
We are failing with
Step(s) to reproduce
Reruning the job is reproducing
Technical details
I've run the steps on the base docker container, and it's working as expected. So it doesn't seem to be an issue with the base image.
The text was updated successfully, but these errors were encountered: