commit | 7f5e9f70aabb62a61bed4ec24cc0d92d40c02d1f | [log] [tgz] |
---|---|---|
author | Allen Li <ayatane@google.com> | Tue Oct 16 00:25:04 2018 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue Oct 16 03:46:57 2018 |
tree | 18ea7ba5281dcf5e896b0e43b15e58a305b364e6 | |
parent | 36de8aee95b545cb6f951f57676ede4cd5669eec [diff] |
Make log messages less alarming I keep getting bugs about these errors suspected of causing test failures. Reword them so they sound nicer. BUG=chromium:892753 TEST=None Change-Id: Ice95bfefdf5887f5640eb8b764309b4d78613c89 Reviewed-on: https://chromium-review.googlesource.com/1281876 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Aviv Keshet <akeshet@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