| commit | 36a2c180d5e5f295cd4c16c61f6cd881e82b945a | [log] [tgz] |
|---|---|---|
| author | Allen Li <ayatane@google.com> | Tue Oct 10 23:32:08 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Sat Oct 14 00:22:10 2017 |
| tree | c630d3f09c7c686bf8871b331448a22f6bddc40d | |
| parent | 456b4c63e4aff2bf7dc9ae6dc95faee2645eb9ef [diff] |
Clean up lucifer Final sweep through code in preparation for rollout. Mostly documentation changes and refactoring. The only functional changes are: - Addition of multierror - Silence error from ListenForAbort BUG=chromium:748234 TEST=None Change-Id: I65f175c9b6ce788b4fddc9d31594730a1b03d32d Reviewed-on: https://chromium-review.googlesource.com/714456 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Allen Li <ayatane@chromium.org>
Chromium OS test running infrastructure.
The primary binary provided by lucifer is job_shepherd, which implements (or will implement) all parts of running an Autotest job. Updating the status of a running job is delegated to the calling process. job_shepherd prints status update events to stdout, and the calling process should perform the necessary updates.
Setup a development environment:
$ sudo apt-get install go $ export GOPATH=$(pwd)
To serve documentation:
$ godoc -port 5000
To build binaries:
$ make
To run unit tests:
$ make check
To run all tests, including slow and/or flaky tests:
$ make check_all
To check test coverage of a package:
$ scripts/check_coverage chromiumos/infra/lucifer/event