New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 675293 link

Starred by 1 user
Status: Duplicate
Merged: issue 674346
Owner:
█ katthomas@chromium.org
Last visit > 30 days ago
Closed: Dec 2016
Cc:
█ phajdan.jr@chromium.org
dpranke@chromium.org
mar...@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"accessibility_unittests (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Dec 17 2016 
"accessibility_unittests (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 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRhY2Nlc3NpYmlsaXR5X3VuaXR0ZXN0cyAod2l0aCBwYXRjaCkM.

Comment 1 by rjkroege@chromium.org, Dec 17 2016

Cc: dpranke@chromium.org
Components: -Tests>Flaky Infra
Labels: -Via-TryFlakes
Owner: mar...@chromium.org
Status: Assigned (was: Untriaged)
Of the flakes listed here:

try run at 2016-12-16 22:29:34 UTC	(milo)	patchset	linux_chromium_chromeos_ozone_rel_ng	(reported in 675293)
try run at 2016-12-16 22:29:03 UTC	(milo)	patchset	linux_chromium_chromeos_rel_ng	(reported in 675293)
try run at 2016-12-16 22:19:48 UTC	(milo)	patchset	linux_chromium_chromeos_ozone_rel_ng	(reported in 675293)

All of them end with the accessibility_unittests running probably correctly (under swarming) but for some reason the builder hung collecting the results.

maruel@: can you assign appropriately?

Comment 2 by rjkroege@chromium.org, Dec 17 2016 

 Issue 675292  has been merged into this issue.

Comment 3 by wjmaclean@chromium.org, Dec 19 2016

Labels: -Sheriff-Chromium Infra-Troopers

Comment 4 by mar...@chromium.org, Dec 19 2016

Cc: mar...@chromium.org phajdan.jr@chromium.org
Owner: katthomas@chromium.org
The builds are forcibly canceled after 2 hours by the recipe. :(
ex:
https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng/builds/290708
https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_rel_ng/builds/334821

We discussed increasing the per task timeouts (http://go/lower-timeout) but managing slow compilation (1:19 and 1:37 in these examples) was out of scope. IMHO the overall recipe timeout should be relaxed.

Assigning to k@ to triage.

Comment 5 by katthomas@google.com, Dec 19 2016

Labels: Infra-Failures

Comment 6 by katthomas@google.com, Dec 19 2016

Mergedinto: 674346
Status: Duplicate (was: Assigned)

Comment 7 by katthomas@google.com, Jan 25 2017

Labels: Hotlist-Infra-Failures
►

Sign in to add a comment