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

save_analysis: fix some ICEs #73046

Merged
merged 2 commits into from
Jun 8, 2020
Merged

Conversation

marmeladema
Copy link
Contributor

@marmeladema marmeladema commented Jun 5, 2020

Fixes #73020
Fixes #73022
Fixes #73041

@rust-highfive
Copy link
Collaborator

r? @eddyb

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jun 5, 2020
@marmeladema
Copy link
Contributor Author

r? @Xanewok

@rust-highfive rust-highfive assigned Xanewok and unassigned eddyb Jun 5, 2020
@Xanewok
Copy link
Member

Xanewok commented Jun 5, 2020

Good catch, thanks!

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Jun 5, 2020

📌 Commit 84e4777 has been approved by Xanewok

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 5, 2020
@marmeladema marmeladema changed the title save_analysis: fix ice in get_expr_data save_analysis: fix some ICEs Jun 5, 2020
@marmeladema
Copy link
Contributor Author

Sorry @Xanewok i've just added a fix for another issue.

@Xanewok
Copy link
Member

Xanewok commented Jun 5, 2020

Do you think there are going to be more issues with TypeRelative paths being not matched on?

By the way you can try running the entire test suite with -Zsave-analysis passed to considerably increase the test set 😄

@marmeladema
Copy link
Contributor Author

Potentially yes, but i've tried adding it everywhere and it leads to other bugs later on in librustc_middle so it will take a bit of time to understand how to do it properly.

In the mean time, those 2 commits should fix some ices/panics.

@marmeladema
Copy link
Contributor Author

By the way you can try running the entire test suite with -Zsave-analysis passed to considerably increase the test set smile

That's what I am doing right now to find more crashes 👍 I hope to come back with some more patches in the next few days

@Xanewok
Copy link
Member

Xanewok commented Jun 6, 2020

That's good to hear! Let's try to land this, then:

@bors r+

@bors
Copy link
Contributor

bors commented Jun 6, 2020

📌 Commit 4d6a307 has been approved by Xanewok

Dylan-DPC-zz pushed a commit to Dylan-DPC-zz/rust that referenced this pull request Jun 6, 2020
Dylan-DPC-zz pushed a commit to Dylan-DPC-zz/rust that referenced this pull request Jun 6, 2020
RalfJung added a commit to RalfJung/rust that referenced this pull request Jun 6, 2020
RalfJung added a commit to RalfJung/rust that referenced this pull request Jun 6, 2020
RalfJung added a commit to RalfJung/rust that referenced this pull request Jun 6, 2020
@RalfJung
Copy link
Member

RalfJung commented Jun 6, 2020

3 rollups failed with the same error and all contained this PR:
#73052, #73053, #73062
So, I think this is likely the culprit...
@bors r- rollup=never

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jun 6, 2020
@marmeladema
Copy link
Contributor Author

Superseded by #73071

@marmeladema marmeladema closed this Jun 6, 2020
@RalfJung
Copy link
Member

RalfJung commented Jun 6, 2020

(Looks like that's just more commits added to this one, so IMO it would make sense to keep using the same PR so that all discussion is in one place. But whatever.^^)

@marmeladema
Copy link
Contributor Author

The hope is that those new commits will magically fix those weird failures :-D

@RalfJung
Copy link
Member

RalfJung commented Jun 6, 2020

I understand. Still no reason to open a new PR -- to the contrary, opening a new PR erases the prior discussion and thus the relation to the previous failures.

But also, another rollup saw the same failures again and didn't include this PR. I am at a total loss where the problem is coming from.

@marmeladema
Copy link
Contributor Author

I understand and I don't mind to let this PR open as a matter of fact. I thought it would be confusing to have two that includes the same commits.

@marmeladema marmeladema reopened this Jun 6, 2020
@RalfJung
Copy link
Member

RalfJung commented Jun 6, 2020

Yes that's confusing indeed. So why did you open a 2nd one in the first place? You had a perfectly fine PR here, no reason to ditch it. :)

@marmeladema
Copy link
Contributor Author

So @RalfJung let's go as originally planned. Can this be approved again? Or is there still suspicions this PR is breaking CI?

@Xanewok
Copy link
Member

Xanewok commented Jun 6, 2020

@Xanewok
Copy link
Member

Xanewok commented Jun 6, 2020

Thanks a lot! Let's try to get this in again...

@bors r+

@bors
Copy link
Contributor

bors commented Jun 6, 2020

📌 Commit a7c18e0 has been approved by Xanewok

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Jun 6, 2020
@Dylan-DPC-zz
Copy link

@bors p=1

@bors
Copy link
Contributor

bors commented Jun 8, 2020

⌛ Testing commit a7c18e0 with merge 7355816...

@bors
Copy link
Contributor

bors commented Jun 8, 2020

☀️ Test successful - checks-azure
Approved by: Xanewok
Pushing 7355816 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jun 8, 2020
@bors bors merged commit 7355816 into rust-lang:master Jun 8, 2020
@marmeladema marmeladema deleted the save-analysis-fix-path branch April 24, 2021 09:12
@cuviper cuviper added this to the 1.46 milestone May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
9 participants