You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ml-kem lax-checking CI job should be using the same hax commit for extraction and hax-lib. For now it uses the hax commit it is ran against for extraction, but it uses main for hax-lib (because libcrux's Cargo.toml points to hax main). For PRs that make changes to hax-lib we need to run this job using hax-lib from the commit being tested.
The current situation is quite annoying in situations like: #1199 (comment)
The text was updated successfully, but these errors were encountered:
The ml-kem lax-checking CI job should be using the same hax commit for extraction and
hax-lib
. For now it uses the hax commit it is ran against for extraction, but it usesmain
forhax-lib
(because libcrux'sCargo.toml
points to hax main). For PRs that make changes to hax-lib we need to run this job using hax-lib from the commit being tested.The current situation is quite annoying in situations like: #1199 (comment)
The text was updated successfully, but these errors were encountered: