New issue
Advanced search Search tips

Issue 873908 link

Starred by 1 user
Status: Assigned
Owner:
wzang@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

WallpaperPolicyTest.(PRE_)SetResetClear time out

Project Member Reported by shimazu@chromium.org, Aug 14 
Flakiness dashbaord:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&testType=mash_browser_tests&tests=WallpaperPolicyTest

WallpaperPolicyTest.(PRE_)SetResetClear are frequently timed out.
Let me disable the test tentatively.

Comment 1 by shimazu@chromium.org, Aug 14

Components: Tests>Flaky
Owner: achuith@chromium.org
Status: Assigned (was: Untriaged)
Let me assign the owner of the test.
achuith: could you triage this and route this to an appropriate owner?
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 14 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a363eb3832e6e4bbd82a6834fa06824e63735ba6

commit a363eb3832e6e4bbd82a6834fa06824e63735ba6
Author: Makoto Shimazu <shimazu@chromium.org>
Date: Tue Aug 14 03:16:52 2018

Disable flaky WallpaperPolicyTest.SetResetClear

TBR=achuith@chromium.org
NOTRY=true

Bug: 873908
Change-Id: I96073584e422833f3aa16c80945f645dcc5d78c2
Reviewed-on: https://chromium-review.googlesource.com/1173832
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582814}
[modify] https://crrev.com/a363eb3832e6e4bbd82a6834fa06824e63735ba6/chrome/browser/chromeos/login/users/wallpaper_policy_browsertest.cc

Comment 3 by xidac...@chromium.org, Aug 15

Labels: -Sheriff-Chromium

Comment 4 by achuith@chromium.org, Dec 10

Owner: x...@chromium.org
Status: Untriaged (was: Assigned)
Daisy, do you know who would be a good owner for this?

Comment 5 by x...@chromium.org, Dec 10

Owner: wzang@chromium.org
wzang@, could you take a look?

Comment 6 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment