| commit | 7c5776b884cf20d549d96ac01f8dbc78fc14f9e2 | [log] [tgz] |
|---|---|---|
| author | Allen Li <ayatane@google.com> | Tue Feb 06 02:17:24 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Feb 06 20:21:22 2018 |
| tree | e61e190ba0106a8d4c6032dc62a7393a784d7ef2 | |
| parent | a79e199104c1a4fbd771371f02e5445d5f044774 [diff] |
Add error handling for sending events Ugly case of ignored errors. The effect of this bug is that lucifer would not terminate if the parent dies, instead running to completion even though that completion wont be sent to Autotest. The parent will still wait for lucifer to terminate; it would just take longer than it should. Undesirable, but not fatal. BUG=chromium:799633 TEST=None Change-Id: I2b27e03633796e834b2bc96e55973340c9ce5f74 Reviewed-on: https://chromium-review.googlesource.com/903546 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