-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Upgrade Travis to using Xenial environment #1149
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
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
Well, it didn't fix #1148 (see https://travis-ci.org/rust-lang/libc/jobs/459211639). OTOH once Travis fix whatever #1148 actually is in their underlying infrastructure, this would then be worth merging still |
@bors: r+ Maybe Travis/docker had a bad weekend? |
📌 Commit e73f064 has been approved by |
Upgrade Travis to using Xenial environment One part "lets use the latest things", to several parts "might this fix #1148"
💔 Test failed - status-travis |
This appears to have broken for different reasons:
Not entirely sure either of those are Xenial-related given the earlier working build |
@bors: retry Yeah looks spurious! |
Upgrade Travis to using Xenial environment One part "lets use the latest things", to several parts "might this fix #1148"
☀️ Test successful - status-appveyor, status-travis |
One part "lets use the latest things", to several parts "might this fix #1148"