Skip to content
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

error[E0080]: evaluation of constant value failed #3672

Closed
Meemaw opened this issue Aug 25, 2023 · 3 comments
Closed

error[E0080]: evaluation of constant value failed #3672

Meemaw opened this issue Aug 25, 2023 · 3 comments

Comments

@Meemaw
Copy link
Contributor

Meemaw commented Aug 25, 2023

Describe the bug
Seeing these errors since last night. No changes on our side, this just started failing. Probably some unpinned dependency.

error[E0080]: evaluation of constant value failed
    --> /Users/x/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v8-0.71.2/src/isolate.rs:1715:3
     |
1715 |   assert!(size_of::<TypeId>() == size_of::<u64>());
     |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'assertion failed: size_of::<TypeId>() == size_of::<u64>()', /Users/x/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v8-0.71.2/src/isolate.rs:1715:3
     |
     = note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
     
...


For more information about this error, try `rustc --explain E0080`.
error: could not compile `v8` (lib) due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `v8` (lib) due to previous error

Any ideas?

@Meemaw
Copy link
Contributor Author

Meemaw commented Aug 25, 2023

I see this is failing in your repo as well ~ on the latest PR: #3671

CI Run: https://app.circleci.com/pipelines/github/apollographql/router/14826/workflows/52095d11-eba9-4d24-b41a-2283854e0640/jobs/97028

@Meemaw
Copy link
Contributor Author

Meemaw commented Aug 25, 2023

Seems to be due to Rust 1.72.0 pinning toolchain to 1.71.1 fixed the issue for us.

@abernix
Copy link
Member

abernix commented Aug 28, 2023

Thanks for opening this! I'll close this as a duplicate of #3684, which has a reproduction.

@abernix abernix closed this as not planned Won't fix, can't repro, duplicate, stale Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants