-
Notifications
You must be signed in to change notification settings - Fork 4
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
Nayduck nightly build is broken #3
Comments
Looks like cargo is broken. This fails:
while this works:
|
@mina86 does that mean one of |
Those packages do not define those features. I’m pretty sure that running the two commands separately is a valid solution. |
The above works for the listed packages but there’s also issue with:
Building all but the
Part of the issue is rust-lang/cargo#6915 which prevents features from selecting features on dev-dependencies. |
@mina86 so maybe we should tackle near/nearcore#4357 first |
I’m not entirely sure why, but build fails when building all the packages together: cargo build -p neard -p genesis-populate -p restaked \ -p near-test-contracts --features adversarial \ --features nightly_protocol,nightly_protocol_features […] error[E0063]: missing field `evm_chain_id` in initializer of `ApplyState` --> test-utils/testlib/src/user/runtime_user.rs:131:9 | 131 | ApplyState { | ^^^^^^^^^^ missing `evm_chain_id` error[E0063]: missing field `evm_chain_id` in initializer of `ViewApplyState` --> test-utils/testlib/src/user/runtime_user.rs:246:26 | 246 | let view_state = ViewApplyState { | ^^^^^^^^^^^^^^ missing `evm_chain_id` error: aborting due to 2 previous errors However, things work fine if `neard` is built separately from the other packages. It has to do with `protocol_feature_evm` which is not enabled in `testlib` when necessary. Whatever the case may be, split the build into two commands. Fixes: #3
Nightly build is broken. See http://nayduck.eastus.cloudapp.azure.com:3000/#/build/1469 for example
The text was updated successfully, but these errors were encountered: