-
Notifications
You must be signed in to change notification settings - Fork 120
test_no_warnings broken on newer stable Rust #416
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
Comments
Nothing in the release notes stands out. |
I suspect this changed in rust-lang/rust#29973 . |
brendanzab
added a commit
that referenced
this issue
May 21, 2017
This is a termporary fix for #416 - not sure if these aliases are actually needed :/
brendanzab
added a commit
that referenced
this issue
May 21, 2017
This is a termporary fix for #416 - not sure if these aliases are actually needed :/
brendanzab
added a commit
that referenced
this issue
May 21, 2017
This is a temporary fix for #416 - not sure if these aliases are actually needed :/
Added fixes to a bunch of issues in #417. Thanks for giving me a kick to get back to some housework! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My PR (#415) failed Travis, and per #411 (comment) the last Travis build on master was almost 6 months ago. January 14th, 2017, to be specific: a76dce4
It looks like this test was broken in Rust 1.15. I installed a few older releases via rustup and worked backwards until it passed, which it did with Rust 1.14:
Rust 1.14 results
and it fails with Rust 1.15:
Rust 1.15 results
Rust 1.15 was released Febuary 2nd, 2017, so the timing lines up as well.
The text was updated successfully, but these errors were encountered: