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

Document how to generate UI test .stderr files locally #464

Open
joshlf opened this issue Oct 4, 2023 · 0 comments
Open

Document how to generate UI test .stderr files locally #464

joshlf opened this issue Oct 4, 2023 · 0 comments
Labels
compatibility-nonbreaking Changes that are (likely to be) non-breaking

Comments

@joshlf
Copy link
Member

joshlf commented Oct 4, 2023

As uncovered in #183 and rust-lang/rust#116433, rustc's output - when run on our UI test files - differs depending on whether the rust-src component is installed for a given toolchain. As of #183, we require that component to be installed in CI, and so a developer testing or generating .stderr files locally must also have it installed. It doesn't always get installed by default, which can be a source of confusion (the resulting error is mysterious and gives no hints that rust-src is the culprit).

We should document this somewhere so that developers aren't confused.

@joshlf joshlf added the compatibility-nonbreaking Changes that are (likely to be) non-breaking label Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility-nonbreaking Changes that are (likely to be) non-breaking
Projects
None yet
Development

No branches or pull requests

1 participant