"remote_run_result" is flaky |
||||||
Issue description"remote_run_result" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHAsSBUZsYWtlIhFyZW1vdGVfcnVuX3Jlc3VsdAw. The chromium-try-flakes app is able to file bugs for individual tests when the test launcher is uploading results to the Test Results Server. If recent flakes above are caused by failing tests and you would like to have them filed as invidual bugs, please read more at https://goo.gl/QJKXV4. This flaky test/step was previously tracked in issue 719285 .
,
May 18 2017
These failures seem like they should be being treated as infra failures, and not flaky steps, maybe? sergiyb@, can you take a look?
,
May 18 2017
Indeed looks like an infra thing, hence taking out of the sheriff queue.
,
May 18 2017
Infra failure is also a failure and the step is flaky (some other build on the same CL passes). At first I though it's duplicating failure in some other step (as "steps" does), but I've found a build https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_swarming_rel/builds/179716, where it's the only step failing. Therefore, we need to find an owner to fix infra failures.
,
May 18 2017
iannucci, any idea how come recipe engine not dump a result file?
,
May 19 2017
All three of these instances are crashing during bootstrap: * https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_swarming_rel/builds/179703/steps/update_scripts/logs/stdio * https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Ftryserver.chromium.android%2Fandroid_n5x_swarming_rel%2F179716%2F%2B%2Frecipes%2Fstderr * https://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-generic_chromium_compile_only_ng/builds/340862/steps/update_scripts/logs/stdio I'm not sure what the errors asking about lighttpd or python-rsa are about though...
,
May 19 2017
At least one of these machines has some .pyc files which are marked read-only and can't be deleted by chrome-bot
,
May 19 2017
So is /b/slave.DEPS/.git/FETCH_HEAD. This bot is borked, respawning.
,
May 19 2017
I've respawned the machines with bad permissions and the other one looks like a simple flake. I'm prepping a CL to get better diagnostics when that sort of flake happens.
,
May 22 2017
Sounds like #6 fixed the source of the flakes. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dmazz...@chromium.org
, May 17 2017