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

Doc Build Failure: ICE: index out of bounds: the len is 1 but the index is 2 #1771

Closed
Nemo157 opened this issue Jul 16, 2022 · 3 comments
Closed
Labels
C-build-failure Category: This is a crate that failed to build S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work.

Comments

@Nemo157
Copy link
Member

Nemo157 commented Jul 16, 2022

Current nightly has an ICE that hits a widely used dependency (time), causing over half of the recent build failures. Once this is fixed we will rebuild all crates affected. First affected nightly was rustc 1.64.0-nightly (c2f428d2f 2022-07-14).

@Nemo157 Nemo157 added C-build-failure Category: This is a crate that failed to build S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work. labels Jul 16, 2022
@Nemo157 Nemo157 pinned this issue Jul 16, 2022
@syphar
Copy link
Member

syphar commented Jul 23, 2022

@Nemo157 it looks like the ICE was fixed in the meantime, does it?

Which would be the first fixed nightly , coming from the merge time of the fix?

Then I could just query all failed builds for these and requeue them.

Or were you planning on grepping the logs?

@Nemo157
Copy link
Member Author

Nemo157 commented Jul 23, 2022

Yep, it should be fixed in the 2022-07-17 toolchain. I'm running my scrape-recent-failures 2022-07-13 "index out of bounds: the len is 1 but the index is 2', compiler/rustc_builtin_macros" script right now to grab all the builds affected by this. (I should add a similar command to the binary so we can do the check on the server and queue them straight away instead of going over the web, though I guess it still needs to hit S3 for each build-log).

@Nemo157
Copy link
Member Author

Nemo157 commented Jul 23, 2022

Queued new builds for:

salvo 0.27.0
salvo_extra 0.27.0
salvo_core 0.27.0
aim 1.5.2
pooly 0.2.1
orly 0.1.3
tracing-init 0.1.0
release_plz_core 0.2.18
clyde 0.1.0
disarray 0.1.11
poem-dbsession 0.3.35
poem-openapi 2.0.5
poem 1.3.35
wasmbus-rpc 0.9.3
rsonpath 0.1.0
wasmcloud-test-util 0.4.1
wasmcloud-control-interface 0.16.2
rsonpath 0.1.0
datapack 2.0.1
cobble-core 0.4.1
mungos 0.2.12

@Nemo157 Nemo157 unpinned this issue Jul 23, 2022
@Nemo157 Nemo157 closed this as completed Jul 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-build-failure Category: This is a crate that failed to build S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work.
Projects
None yet
Development

No branches or pull requests

2 participants