| commit | 72e57c833969c9c4fab5c65ec5c5c3dca68be177 | [log] [tgz] |
|---|---|---|
| author | Allen Li <ayatane@google.com> | Wed Nov 15 22:18:55 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Nov 16 21:52:03 2017 |
| tree | 2b78420df39615f39085e6634cd9d1a1514900c4 | |
| parent | 865f3d396171c434592713d07eda78614ff040ef [diff] |
Fix abort race condition Mea culpa, assigning a boolean value is not goroutine safe. BUG=chromium:784564 TEST=make check Change-Id: I3b474249df7ebdfba632fe0dbc7524b86223e59c Reviewed-on: https://chromium-review.googlesource.com/772940 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 primary binary provided by lucifer is lucifer_run_job, 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. lucifer_run_job 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