| commit | f60e4268429376ccd144fa23764b2b1d0e91159b | [log] [tgz] |
|---|---|---|
| author | Brian Norris <[email protected]> | Tue Apr 16 19:17:11 2024 |
| committer | Chromeos LUCI <[email protected]> | Fri Aug 23 21:59:53 2024 |
| tree | 0c7d917a2206ac672d74281499b5126d55f6fe99 | |
| parent | cd8b65ecbf4aff9525af2304a35b29865164cb36 [diff] |
CHROMIUM: tests: Add TEST_RUN_COMMAND() We're seeing failures like this: ...system shutdown: 2 jobs (1 long-running job which ignores SIGTERM, 1 which starts on session-end and ignores SIGTERM) BAD: wrong value for lines, expected 1 got 0 at tests/test_initctl.c:12068 (test_quiesce). FAIL test_initctl (exit status: 134) These may be command failures, but we don't get the exit status. Let's tweak RUN_COMMAND() to support retrieving the status, and TEST_RUN_COMMAND() for the common case where we want assert a particular exit code. BUG=b:360841319 TEST=cros_run_unit_tests Change-Id: I91523269c1cb9a54d9e8a2dcd95b48432bf25721 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/upstart/+/5805752 Reviewed-by: Allen Webb <[email protected]> Commit-Queue: Allen Webb <[email protected]> Auto-Submit: Brian Norris <[email protected]> Commit-Queue: Brian Norris <[email protected]> Tested-by: Brian Norris <[email protected]>