-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix(test): Add OpenCL deps to Cache Dependencies
workflow
#12423
Conversation
Here's what I think is going on:
I think the fix here is to remove the block you added, but add in this to the |
@rjan90 : I assume we're using this PR to track this issue. Has all of Rod's feedback/suggestions been incorporated, or is there more we need to here? |
FIL Slack conversations on this: |
d0319c0
to
b52792a
Compare
6902973
to
53bab69
Compare
chore(ci): capture build logging and CPU flags
#12440 seems to address the problem here - instead of using the install-filcrypto script (invoked via the Fixing it this way seems reasonable for now but it's a pretty manual hack for something that we should be able to do with |
Ref: filecoin-project/lotus#12423 Builds using the same flags as rust/scripts/build-release.sh does when called from CI to build the release bundle.
Ref: filecoin-project/lotus#12423 Builds using the same flags as rust/scripts/build-release.sh does when called from CI to build the release bundle.
fix: update account.State import in migration test
* chore(deps): use new FFI_PORTABLE flag for filecoin-ffi builds * chore: update FFI to v1.30.0-dev chore: update FFI to v1.30.0-dev --------- Co-authored-by: Phi <[email protected]>
I have fixed the itest-migration failure in 742635a. Only thing missing now is:
|
You could just fix the codeql check, in multisig/actor.go.template at the top of if id > uint64(math.MaxInt64) {
return nil, xerrors.Errorf("transaction ID %d is out of range for int64", id)
} it's only used for actors v0 so it's pretty silly to have to mess with this each time, in fact just pulling in |
nothing to include, that's all done here and that PR can be closed when this is merged |
I tried to remove a couple of the additions and reversion that were in consecutive commits. But rebasing this PR now is hard because there are recorded submodule modifications which conflicts with the rebase operation. So I think the easier path to get a clean commit history, is to cherry-pick the needed commits over to: #12419 |
Closing as the relevant changes here has been added/cherry-picked into: #12455 |
Related Issues
[Do not merge]
The
Cache Dependencies
test is failing in #12419.Checklist
Before you mark the PR ready for review, please make sure that: