| commit | 3b5a60c60065543344958f73daefffd55308d4ea | [log] [tgz] |
|---|---|---|
| author | Allen Li <ayatane@google.com> | Sat Mar 02 01:13:03 2019 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Mar 04 21:50:16 2019 |
| tree | cd088350283b5a3bbb0dfccc56645ac9dba501d3 | |
| parent | 8350350a2b2485745c2200ca173467c74235a4a7 [diff] |
Put metric errors into a labeled log BUG=chromium:934855 TEST=None Change-Id: Ib3909118999e0d10c531c846e2cc30be32e37d56 Reviewed-on: https://chromium-review.googlesource.com/1497290 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Chromium OS test running infrastructure.
The project provides multiple binaries.
lucifer_run_job and lucifer_admin_task are the main Lucifer binaries. They run a test job and admin task, respectively. They are intended to be run by a parent wrapper process. The commands print status update events to stdout, and the calling process should perform the necessary updates for the scheduling system in use (e.g. Autotest or Swarming).
skylab_swarming_worker is such a wrapper for Swarming.
See Go in Chromium OS. Development should be done in the chroot to ensure the right version of Go and dependencies are used.
To install dependencies, run in the chroot:
sudo emerge -o lucifer