travis: Attempt to fix Android flakiness #38619
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There's been some flaky runs on Travis where the Android emulator is having problems staying alive... presumably? For example: * https://travis-ci.org/rust-lang/rust/jobs/186736745 This commit spawns the emulator in the same way as buildbot with `nohup` to hope that it goes into the background successfully, followed by a `wait-for-device` command. I'm not actually sure if this'll fix the problems we're seeing, but I figure it can't hurt to test out.
|
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
This was referenced Dec 26, 2016
|
@bors r+ p=2 |
|
📌 Commit 35420b0 has been approved by |
|
⌛ Testing commit 35420b0 with merge 6fe064c... |
|
💔 Test failed - status-travis |
|
@bors: retry
* network error
…On Wed, Dec 28, 2016 at 12:14 PM, bors ***@***.***> wrote:
💔 Test failed - status-travis
<https://travis-ci.org/rust-lang/rust/builds/187294477>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#38619 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95Lp16P6MISm2-xLWoYX8sIokE-amks5rMsMXgaJpZM4LV41_>
.
|
|
⌛ Testing commit 35420b0 with merge bc4af67... |
|
💔 Test failed - status-travis |
|
… On Wed, Dec 28, 2016 at 4:25 PM, bors ***@***.***> wrote:
💔 Test failed - status-travis
<https://travis-ci.org/rust-lang/rust/builds/187333956>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#38619 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95GIPMhxAQFIeMLlII7oB5eKOg72Aks5rMv3qgaJpZM4LV41_>
.
|
bors
added a commit
that referenced
this pull request
Dec 29, 2016
travis: Attempt to fix Android flakiness There's been some flaky runs on Travis where the Android emulator is having problems staying alive... presumably? For example: * https://travis-ci.org/rust-lang/rust/jobs/186736745 This commit spawns the emulator in the same way as buildbot with `nohup` to hope that it goes into the background successfully, followed by a `wait-for-device` command. I'm not actually sure if this'll fix the problems we're seeing, but I figure it can't hurt to test out.
|
☀️ Test successful - status-appveyor, status-travis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's been some flaky runs on Travis where the Android emulator is having
problems staying alive... presumably? For example:
This commit spawns the emulator in the same way as buildbot with
nohupto hopethat it goes into the background successfully, followed by a
wait-for-devicecommand. I'm not actually sure if this'll fix the problems we're seeing, but I
figure it can't hurt to test out.