Some swarming test failure are picked up as timeout |
||
Issue descriptionFor example, https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.11%20Tests/25600, browser_tests is purple, and the text shows "some shards did not complete: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9", which indicates that there is a timeout. However, if look at each individual swarming task, they are all test failures instead of timeout: https://chromium-swarm.appspot.com/task?id=3d1523af19404c10&refresh=10&show_raw=1
,
Apr 26 2018
I 'spose I can take a stab at this if my shift allows time for it. Prob involves a fix to https://codesearch.chromium.org/chromium/build/scripts/slave/recipe_modules/swarming/resources/standard_gtest_merge.py
,
Apr 26 2018
We should also try to ensure that base/test/launcher emits something -- maybe an empty JSON -- in this case.
,
Apr 26 2018
Eh, if it's got no results to report, it probably shouldn't be reporting results. Besides, *something* in the task can always go wrong before the json file gets created. True and proper fix lies in the recipe's result collection IMO. |
||
►
Sign in to add a comment |
||
Comment 1 by bpastene@chromium.org
, Apr 26 2018