-
Notifications
You must be signed in to change notification settings - Fork 0
add rust nightly for hax, allow lean to fail - wip #1
New issue
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
base: main
Are you sure you want to change the base?
Conversation
|
|
||
| ## Why it currently fails in CI: | ||
|
|
||
| - Installing hax from crates.io (cargo install cargo-hax --version 0.3.5) on the pinned nightly fails due to mismatches with rustc internals (e.g., missing/renamed types like CanonicalTyVarKind, DynKind, AssocItemContainer). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this then not work locally? If it is working locally, How is the local setup different than CI?
|
|
||
| ## What kind of help we need from DevOps: | ||
|
|
||
| - Help pin and install a consistent hax toolchain in CI. Most likely we need to install hax from the same git revision as our local working checkout (not the crates.io 0.3.5 package), e.g. cargo install --git ... --rev <HAX_REV> cargo-hax and the companion binaries, using the pinned nightly nightly-2025-11-08. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah can we document this.
My suggestion is following our convention of defining
dependencies that are not submodules within a folder at the root deps/<depName>
Within the file is ideally a stable git-tag if not available for the dependent then referencing a git-sha.
We'll then build up CI references around that for stability / consistency / documented in revision history
| ## What kind of help we need from DevOps: | ||
|
|
||
| - Help pin and install a consistent hax toolchain in CI. Most likely we need to install hax from the same git revision as our local working checkout (not the crates.io 0.3.5 package), e.g. cargo install --git ... --rev <HAX_REV> cargo-hax and the companion binaries, using the pinned nightly nightly-2025-11-08. | ||
| - Confirm CI network policy: whether we can fetch from GitHub directly or need a mirrored/internal repo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this repository specifically?
Best options are
- If making contributions to the dependent then a fork + use as a submodule (when building src requires the dependent src)
- If just a library set of scripts or tools needed at runtime, then a reference as mentioned in comment on line 26 above is sufficient.
|
|
||
| - Help pin and install a consistent hax toolchain in CI. Most likely we need to install hax from the same git revision as our local working checkout (not the crates.io 0.3.5 package), e.g. cargo install --git ... --rev <HAX_REV> cargo-hax and the companion binaries, using the pinned nightly nightly-2025-11-08. | ||
| - Confirm CI network policy: whether we can fetch from GitHub directly or need a mirrored/internal repo. | ||
| - (Optional) Add caching for ~/.cargo/{git,registry,bin} and a dedicated CARGO_TARGET_DIR to speed up tool installs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This appears done based on the code in this review.
changes to fix CI: add rust nightly for hax, allow lean to fail - wip