New issue
Advanced search Search tips

Issue 798774 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"content_shell_crash_test (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jan 3 2018

Issue description

"content_shell_crash_test (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 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 14 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMAsSBUZsYWtlIiVjb250ZW50X3NoZWxsX2NyYXNoX3Rlc3QgKHdpdGggcGF0Y2gpDA.

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 741766 .
 
Components: Infra
Status: Available (was: Untriaged)
Could infra folks take a look?

I looked at this instance:
https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/615998

The error message is:
some shards did not complete: 0
shard #0 expired, not enough capacity

Comment 2 by mmoss@chromium.org, Jan 3 2018

Mergedinto: 798579
Status: Duplicate (was: Available)
Looks like the failures were all yesterday afternoon/evening, probably related to swarming problems in Issue 798579.

Sign in to add a comment