Investigate if "BOARD_NOT_AVAILABLE" occurs when there are DUTS in a pool. |
|||
Issue descriptionThis build skipped testing because there were no duts. However, when there are no duts, we are supposed to skip testing, but aren't supposed to kill the build. What happened? https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_skate-paladin/builds/7547 04:09:02: WARNING: Exception is not retriable return code: 5; command: /b/cbuild/internal_master/chromite/third_party/swarming.client/swarming.py run --swarming chromeos-proxy.appspot.com --task-summary-json /tmp/cbuildbot-tmp4ofGiD/tmpykCNb2/temp_summary.json --raw-cmd --task-name daisy_skate-paladin/R54-8737.0.0-rc1-bvt-inline --dimension os Ubuntu-14.04 --dimension pool default --print-status-updates --timeout 9000 --io-timeout 9000 --hard-timeout 9000 --expiration 1200 -- /usr/local/autotest/site_utils/run_suite.py --build daisy_skate-paladin/R54-8737.0.0-rc1 --board daisy_skate --suite_name bvt-inline --pool cq --num 6 --file_bugs False --priority CQ --timeout_mins 90 --retry True --max_retries 10 --minimum_duts 4 --offload_failures_only True -c Priority was reset to 100 Triggered task: daisy_skate-paladin/R54-8737.0.0-rc1-bvt-inline chromeos-server31-250: 30d50e9b4f517a10 5 Autotest instance: cautotest /usr/local/autotest/site_utils/run_suite.py:1712: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 output_dict['return_message'] = 'Skipping testing: %s' % e.message Skipping testing: No hosts found for board:daisy_skate in pool:cq. The test lab currently does not cover test for this board and pool. Will return from run_suite with status: BOARD_NOT_AVAILABLE
,
Aug 30 2016
> This build skipped testing because there were no duts. > However, when there are no duts, we are supposed to skip > testing, but aren't supposed to kill the build. When there are no DUTs, run_suite.py returns status "BOARD_NOT_AVAILABLE". The canaries treat this status as "success". The CQ treats this status as "failure". That's the currently programmed behavior. I think it's right, but I could be wrong about that. However, I don't fully understand why this happened: BOARD_NOT_AVAILABLE means there were no DUTs assigned to the pool. Yet, there are and should then have been assigned DUTs. If all the DUTs were broken, that's meant to give a different error status.
,
Sep 7 2016
Not sure we can get the right logs at this point, but seems like it would be a good investigation to see if we're doing this right. Marking as FixIt.
,
Mar 10 2018
This bug has not been touched in over a year. It is probably no longer relevant. |
|||
►
Sign in to add a comment |
|||
Comment 1 by aut...@google.com
, Aug 30 2016