"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 17 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 726978 .
,
Jun 9 2017
huangs@, why is this assigned to me?
,
Jun 9 2017
Because I'm a Sheriff. Searching "remote_run_result" leads to //build/scripts/slave/remote_run.py. You made the last 6 changes to the file, so to the least you'd have better idea whom to triage this to. CC'ing other Sheriffs.
,
Jun 9 2017
Ah, I see. Unfortunately, the "remote_run_result" is a red herring. If you look at one of the failing builds, you'll see this error message:
@@@STEP_LOG_LINE@exception@Traceback (most recent call last):@@@
@@@STEP_LOG_LINE@exception@ File "../../../scripts/slave/remote_run.py", line 635, in shell_main@@@
@@@STEP_LOG_LINE@exception@ return main(argv, stream)@@@
@@@STEP_LOG_LINE@exception@ File "../../../scripts/slave/remote_run.py", line 604, in main@@@
@@@STEP_LOG_LINE@exception@ cleanup_temp.Cleanup(b_dir=basedir)@@@
@@@STEP_LOG_LINE@exception@ File "E:\b\build\scripts\slave\cleanup_temp.py", line 240, in Cleanup@@@
@@@STEP_LOG_LINE@exception@ _CleanupWindows(b_dir=b_dir)@@@
@@@STEP_LOG_LINE@exception@ File "E:\b\build\scripts\slave\cleanup_temp.py", line 173, in _CleanupWindows@@@
@@@STEP_LOG_LINE@exception@ check_free_space_path('e:\\')@@@
@@@STEP_LOG_LINE@exception@ File "E:\b\build\scripts\slave\cleanup_temp.py", line 153, in check_free_space_path@@@
@@@STEP_LOG_LINE@exception@ raise FullDriveException(path, free_space)@@@
@@@STEP_LOG_LINE@exception@FullDriveException@@@
@@@STEP_LOG_END@exception@@@
@@@STEP_EXCEPTION@@@
The problem here is a "FullDriveException" exception, which suggests that the bot's disk drive is full. I will add this to the trooper queue for you, for the current trooper to handle.
For future sheriffing and triage, it is a good idea to look at a few example failures and see if you can identify any underlying cause before choosing an owner.
,
Jun 9 2017
Actually since I'm here, the flakes were identified on builds that referenced the following bots: - vm761-m4 - vm1257-m4 - vm335-m4 - vm831-m4 - vm403-m4 Looking at each bot, all of them have had several successful builds, indicating that the "disk full" state is no longer a problem. I suspect that this *is* related to something that I did, namely adding code yesterday that automatically cleaned up more stuff on bots and, consequently, fixed them automatically. Since every reported error case seems to have resolved itself, I'm going to mark this Fixed.
,
Jun 9 2017
An nice. Thanks for taking care of this! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by hua...@chromium.org
, Jun 9 2017Status: Assigned (was: Untriaged)