Report 'NO_RESOURCE' correctly in run_suite_skylab |
|||
Issue descriptionIt should be a test failure: https://chrome-swarming.appspot.com/task?id=3ea86968e6c2f610&refresh=10 But it's not well reported.
,
Jul 13
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/579f6295ed02a560e0fd0d0d77620d5e668bb206 commit 579f6295ed02a560e0fd0d0d77620d5e668bb206 Author: Xixuan Wu <xixuan@chromium.org> Date: Fri Jul 13 19:00:45 2018 autotest: Report NO_RESOURCE as infra failure of suite Currently test failure caused by 'NO_RESOURCE' is reported as success. This CL changes it to report as infra failure. BUG= chromium:863207 TEST=None Change-Id: Id4c72dd94744f3027f0a66c9c2357fbfe4823675 Reviewed-on: https://chromium-review.googlesource.com/1135926 Commit-Queue: Xixuan Wu <xixuan@chromium.org> Tested-by: Xixuan Wu <xixuan@chromium.org> Reviewed-by: Allen Li <ayatane@chromium.org> [modify] https://crrev.com/579f6295ed02a560e0fd0d0d77620d5e668bb206/venv/skylab_suite/suite_tracking.py
,
Jul 17
Seems like this is needed in the current phase (mark skylab-based paladin important) Already fixed?
,
Jul 19
|
|||
►
Sign in to add a comment |
|||
Comment 1 by xixuan@chromium.org
, Jul 12