Repository navigation
Key the opam cache on the opam that reads it - #32
Merged
Merged
Conversation
setup-ocaml@v3 installs the latest opam release, which moved from 2.5.2
to 2.6.0 on 2026-09-17. The restored ~/.opam still had the older root
layout, so the first opam command after the restore upgraded it,
printed "Update done, please now retry your command." and exited 10.
Both Frama-C lanes failed at that step ("Install cppo" and "Check
installed Frama-C version"). Re-running did not help, because a failed
job never saves the upgraded root.
Both cache keys now include "opam --version". A new opam release
starts from a cold cache once instead of breaking every run. The
bubblewrap "Sandboxing is not working" error in the same log is not
the cause: opam answers yes and runs without the sandbox.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
jserv
reviewed
Sep 18, 2026
jserv
reviewed
Sep 18, 2026
The command substitution sat inside echo, so the step took echo's exit status. An opam that failed wrote "version=", the step passed, and the key fell back to "Linux-opam--ocaml-...", one entry shared by every opam release, which is the collision the key exists to prevent. A bare assignment carries the substitution's status, and run: uses bash -e, so the step now fails at the point where opam failed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
setup-ocaml@v3 installs the latest opam release, which moved from 2.5.2 to 2.6.0 on 2026-09-17. The restored
~/.opamstill had the older root layout, so the first opam command after the restore upgraded it, printedUpdate done, please now retry your command.and exited 10:ast-utils plugin + Frama-C 33.0failed atInstall cppoast-utils plugin on the supported floorfailed atCheck installed Frama-C versionRe-running does not help, because a failed job never saves the upgraded root (run 35336549042, attempts 1 and 2).
Both opam cache keys now include
opam --version. A new opam release starts from a cold cache once (about 10 minutes of Frama-C build) instead of breaking every run.The
Sandboxing is not working ... bwrap: loopback: Failed RTM_NEWADDRline in the same log is not the cause. opam answersyto disabling the sandbox, and thesetup-ocamlstep, which prints the same line, succeeds.Summary by cubic
Keys the opam cache on the opam version that reads it, so a new opam release stops breaking the Frama-C build lanes. When opam moved from 2.5.2 to 2.6.0, restored cache roots kept the old layout and the first opam command after restore failed with
Update done, please now retry your command.(exit 10); re-running doesn't help because a failed job never saves the upgraded root.Both cache keys now include
opam --version, so a new release starts from a cold cache once. The version step now fails ifopam --versionfails instead of writing an empty version, which would have collapsed all releases into one shared cache key.Note
Sandboxing is not workingwarning in the same logs is unrelated; opam disables the sandbox and continues.Written for commit 9ad7245. Summary will update on new commits.