-
Notifications
You must be signed in to change notification settings - Fork 359
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
doctests in libcore sometimes use wrong external crate #1852
Comments
I think this issue belongs to https://github.com/rust-lang/miri-test-libstd. |
Ah I see, thanks. I can't transfer issues there so I'll do that by hand. |
Moved to rust-lang/miri-test-libstd#4 |
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Jul 17, 2021
fix typo in compile_fail doctest Fixes a typo introduced by rust-lang#86211. For some reason this typo makes Miri go all crazy when running libcore doctests (rust-lang/miri#1852). Kudos to `@hyd-dev` for noticing the typo. Cc `@tlyu` `@joshtriplett`
JohnTitor
added a commit
to JohnTitor/rust
that referenced
this issue
Jul 18, 2021
fix typo in compile_fail doctest Fixes a typo introduced by rust-lang#86211. For some reason this typo makes Miri go all crazy when running libcore doctests (rust-lang/miri#1852). Kudos to ``@hyd-dev`` for noticing the typo. Cc ``@tlyu`` ``@joshtriplett``
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Under some circumstances, Miri goes all crazy on libcore doctests: it seems to load two distinct copies of libcore and then hell breaks loose.
Specifically, this seems to be triggered when the code contains a variable that does not exist -- rustc will try to make szggestions for names to use, which can trigger loading external crates, which might be what is happening here.
The text was updated successfully, but these errors were encountered: