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

Test packaging on android builder #386

Merged
merged 1 commit into from Jun 23, 2016

Conversation

aneeshusa
Copy link
Contributor

@aneeshusa aneeshusa commented May 25, 2016

Our android-nightly builder has been busted for a long time, which meant
our packaging code was not being exercised. Also, the nightly builder
only runs once a day instead of on each build, which recently allowed
a regression to slip in due to an uncaught syntax error. To prevent
future regressions, test packaging on the android builder, which runs
on try and auto builds.

See servo/servo#11406 for the bug.
This should not be merged until that fix is merged and android-nightly has
had a chance to run, to ensure that packaging is no longer broken.


This change is Reviewable

@edunham
Copy link
Contributor

edunham commented Jun 22, 2016

Removing blocked-on-external as the Android fixes have landed.

@aneeshusa
Copy link
Contributor Author

Re-adding the label because there are still other issues that need to be resolved. Looking at the android nightly output, the next issue is fixing the build script to invoke ./mach package --android instead of just ./mach package now that servo/servo#11210 has landed. Once we get a clean android-nightly run (or at least clean through packaging, the S3 upload can be fixed later), this will get unblocked.

Our android-nightly builder has been busted for a long time, which meant
our packaging code was not being exercised. Also, the nightly builder
only runs once a day instead of on each build, which recently allowed
a regression to slip in due to an uncaught syntax error. To prevent
future regressions, test packaging on the android builder, which runs
on try and auto builds.
@aneeshusa aneeshusa force-pushed the test-android-packaging-on-auto branch from 03ec438 to 3501d17 Compare June 22, 2016 10:57
@aneeshusa
Copy link
Contributor Author

Updated this PR to use the new --android flag to ./mach package.

@aneeshusa
Copy link
Contributor Author

Next blocker is #401.

@larsbergstrom
Copy link
Contributor

@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit 3501d17 has been approved by larsbergstrom

@bors-servo
Copy link
Contributor

⌛ Testing commit 3501d17 with merge 7c2eeb8...

bors-servo pushed a commit that referenced this pull request Jun 23, 2016
…bergstrom

Test packaging on android builder

Our android-nightly builder has been busted for a long time, which meant
our packaging code was not being exercised. Also, the nightly builder
only runs once a day instead of on each build, which recently allowed
a regression to slip in due to an uncaught syntax error. To prevent
future regressions, test packaging on the android builder, which runs
on try and auto builds.

See servo/servo#11406 for the bug.
This should not be merged until that fix is merged and android-nightly has
had a chance to run, to ensure that packaging is no longer broken.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/386)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

☀️ Test successful - travis

@bors-servo bors-servo merged commit 3501d17 into servo:master Jun 23, 2016
@aneeshusa
Copy link
Contributor Author

It looks like this change was deployed to servo-master1 without rolling out #388 to the cross builders, causing breakage like http://build.servo.org/builders/android/builds/1582. Please run a full highstate on the builders - I saw that there were some uncommitted changes in /srv/salt and didn't want to overwrite anything. This is why I wanted to wait for android-nightly to build cleanly.

@larsbergstrom
Copy link
Contributor

I thought it was rolled out, but it turned out that servo-linux-cross2 had a broken apt repo and it was preventing the salt upgrade. So I've fixed that manually and things seem right.

I also discovered the dirty bits in /srv/salt were the same as those in #405, so I just reverted them and pulled master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants