-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
graphql-client-302-repro segfaults non-deterministically #134028
Comments
the graphql_query_derive macro is stackoverflowing |
I don't think there's anything to discuss here. There are a lot of broken crates in the wild, adding more entries to the list of crates that crater ignores is normal maintenance of the crater codebase. Especially in the case like this where it's just one crate behaving pathologically, we shouldn't hesitate to add it to the crater exclusion list as soon as someone figures out that this is a bug or nondeterminism in the crate. |
I agree that the net outcome here is just to add this to the crater blocklist. However, it seems that @saethlin already added did so in rust-lang/crater@31b9f33. @saethlin , do you have any clues why this addition to the blocklist didn't take effect? |
Nope! Sounds like an issue to file on the crater repo or a question for t-infra in Zulip. |
Ah! I figured it out. It was added as |
This crates' errors are during its build process, not its tests. Discussed in rust-lang/rust#134028.
Sometimes results in:
This happens on crater runs and has been seen in (at least) the following cases:
#121545 #132961 #117589 #114303 #101061 #95953 #82322
I couldn't see an existing bug for this so I thought I should raise one. It may well be a problem in the proc macro, so this may well not be a rustc bug: but if nothing else, we should probably exclude this crate from crater since it causes such confusion.
The text was updated successfully, but these errors were encountered: