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

Add regression test for #89436 #99257

Merged
merged 1 commit into from
Jul 15, 2022
Merged

Conversation

Manishearth
Copy link
Member

I never got around to adding such a test.

In general I think the yoke crate has a bunch of interesting testcases that exercise various edges of the algorithms here, it would be nice if we could simply depend on the crate and add some tests that exercise it, but I don't think that's possible. Do you or @eddyb think there's any use trying to upstream a bunch of common yoke minimal working example code to the testsuite and having a ton of yoke tests?

@rustbot rustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Jul 14, 2022
@rust-highfive
Copy link
Collaborator

r? @Mark-Simulacrum

(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 Jul 14, 2022
@eddyb
Copy link
Member

eddyb commented Jul 14, 2022

it would be nice if we could simply depend on the crate and add some tests that exercise it, but I don't think that's possible

You could make it a dependency of rustc, heh.

But more seriously, how silly does adding it as a perf benchmark sound?
It's not as good but it can still detect regressions, and it might be genuinely useful if you're hitting e.g. trait system slower edge cases (though I doubt you have metaprogramming on the level of e.g. tower).

@jackh726
Copy link
Member

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Jul 15, 2022

📌 Commit 62edbbe has been approved by jackh726

It is now in the queue for this repository.

@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 Jul 15, 2022
bors added a commit to rust-lang-ci/rust that referenced this pull request Jul 15, 2022
Rollup of 6 pull requests

Successful merges:

 - rust-lang#99113 (Simplify [a]rc code a little)
 - rust-lang#99131 (Add label for generic arg (+ APIT) and RPIT callables in `label_fn_like`)
 - rust-lang#99237 (removed unused CSS and unused HTML IDs)
 - rust-lang#99239 (Add myself to the set of people notified when MIR changes.)
 - rust-lang#99241 (Remove comment referring to constness.rs)
 - rust-lang#99257 (Add regression test for rust-lang#89436)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 7976cd6 into rust-lang:master Jul 15, 2022
@rustbot rustbot added this to the 1.64.0 milestone Jul 15, 2022
@Manishearth
Copy link
Member Author

@eddyb seems a bit silly but i'm open to it if the rust team is okay with perf benchmarks that are Actually Compiler Regression Tests

@Manishearth Manishearth deleted the regression branch July 15, 2022 16:08
@Mark-Simulacrum
Copy link
Member

We have a number of crates in cargotest that we fetch a pinned commit of and run cargo test in; that seems like a better fit here?

@Manishearth
Copy link
Member Author

Yeah we could do that! I don't know if the yoke crate has full test coverage of the bugs, but I can make sure we do and go fix that.

(One of the reasons I'm wary of leaving this up to crater is that a lot of these things only show up when using the crate, i.e when building tests, which crater does do, but folks do tend to look at test failures less)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants