"compile (with patch)" is flaky |
||||
Issue description"compile (with patch)" 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 not infrastructure-related (e.g. flaky test), please add Sheriff-Chromium label and change issue status to Untriaged. When done, please remove the issue from Trooper Bug Queue by removing the Infra-Troopers 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. 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 795529 .
,
Jan 4 2018
All of the linked builds just abruptly stop with: ninja: build stopped: subcommand failed. This can't be diagnosed much further than that due to the lack of any other output, but it doesn't seem like an issue with the system. I'll triage it as a ninja issue and move it over to the sheriffs.
,
Jan 4 2018
win7_chromium_rel_ng failures w/ vfork in linking: https://bugs.chromium.org/p/chromium/issues/detail?id=798913
,
Jan 4 2018
Most of the rest of these appear to be low-frequency flakes, including: master restarts; an internal android linker error that should be fixed by the imminent roll to NDK r16; a pnal undefined reference; hanging builds; a recurrence of issue 544127 . Given the low frequency of the rest of the individual issues, I'm WontFixing this. If their frequency increases, we can revisit this.
,
Jan 4 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by chromium...@appspot.gserviceaccount.com
, Jan 3 2018