Builder linux-rel-css Build #9047

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The AnyBranchScheduler scheduler named 'servo-auto' triggered this build

Steps and Logfiles:

1. git update ( 2 secs )
   1. stdio
2. generic generic ( 0 secs )
   1. - no logs -
3. generic_1 generic_1 ( 0 secs )
   1. - no logs -
4. shell 'pkill -x ...' ( 0 secs )
   1. stdio
5. shell__1 './mach clean-nightlies ...' ( 11 secs )
   1. stdio
6. shell__2 './mach clean-cargo-cache ...' ( 0 secs )
   1. stdio
7. shell__3 './etc/ci/clean_build_artifacts.sh' ( 0 secs )
   1. stdio
8. compile ran build --release --with-debug-assertions warnings ( 9 mins, 40 secs )
   1. warnings (1)
9. test ran test-wpt --release --processes 24 --total-chunks 2 --this-chunk 2 --always-succeed ( 12 mins, 20 secs )
   1. - no logs -
10. shell__4 './mach filter-intermittents ...' ( 2 secs )
    1. stdio
    2. filtered-wpt-errorsummary.log
11. shell__5 'bash ./etc/ci/lockfile_changed.sh' ( 0 secs )
    1. stdio
12. shell__6 './etc/ci/clean_build_artifacts.sh' ( 0 secs )
    1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. bors-servo

   lbergstrom+borsohnoyoudont@mozilla.com

Timing:

All Changes:

:

1. Change #83406

   Category	None
   Changed by	bors-servo <lbergstrom+borsohnoyoudont@mozilla.com>
   Changed at	Mon 02 Jul 2018 17:22:25
   Repository	https://github.com/servo/servo
   Project	servo/servo
   Branch	auto
   Revision	1f9b07637ea960f6b3d4004f832951ad9b6b48ed

   Comments

   Auto merge of #21094 - servo:bootstrap-android, r=paul
   
   Add mach bootstrap-android and test-android-startup commands
   
   This adds a `./mach boostrap-android` subcommand that downloads and installs the tools, SDK, NDK,  emulator, and system image for Android. In an environment that can build Servo at all, this should be enough to get all additional dependencies to cross-compile to Android, package an APK, and load it onto a device or an emulator.
   
   At the moment it requires an interactive user to accept the license (and confirm no customization of the emulated virtual device hardware), and then prints environment variables to set for `mach` as well as the command to run to start the emulator (with an already-configured image). A possible next step could be to automate all this, and have `./mach build` run it automatically when needed. (I don’t know if auto-accepting the license is something we should do though.)
   
   This also adds `--emulator` and `--usb` parameters to `./mach install --android` and `./mach run --android`, which tell `adb` what device to pick when both are present. And makes `./mach run --android` print the new process’s PID, for use with e.g. `adb -e logcat --pid 2263`.
   
   Finally, adds the `./mach boostrap-android` subcommand which starts an emulator, installs the APK (it assumes that `mach build` and `mach package` were already executed), runs a single HTML test case, and checks for a message coming from JS through `console.log()` and `adb logcat`.
   
   <!-- Reviewable:start -->
   ---
   This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/21094)
   <!-- Reviewable:end -->

   Changed files

   • .gitignore
   • components/gfx/platform/freetype/android/font_list.rs
   • python/servo/bootstrap_commands.py
   • python/servo/build_commands.py
   • python/servo/command_base.py
   • python/servo/package_commands.py
   • python/servo/post_build_commands.py
   • python/servo/testing_commands.py
   • python/servo/util.py