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

Issue 881755 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

canary not being pushed

Project Member Reported by uekawa@google.com, Sep 7

Issue description

M71 canary push has not happened since 
2018-09-03 03:25	11031.0.0, 

and seems to be stuck around since M71-CANARY-4 (11033.0.0, 70.0.3538.0), (11034.0.0, 70.0.3538.0)

I expect canary to be updated daily.

 
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>Test
I'm not very familiar with the canary release process, but it looks like a number of release builders have been failing recently, due mostly to HWTests.
Cc: abutzier@chromium.org lannm@google.com uekawa@chromium.org
Labels: -Pri-3 Pri-2
Owner: abutzier@chromium.org
If we fail paygen AU tests, we will not push Canary.

However we do seem to be passing on most, so I am not sure why https://cros-goldeneye.corp.google.com/chromeos/console/viewRelease?releaseName=M71-CANARY-10 or https://cros-goldeneye.corp.google.com/chromeos/console/viewRelease?releaseName=M71-CANARY-9 did not push anything.

If this is determined to be a bug in GE, it probably belongs in b/. 
Components: -Infra>Client>ChromeOS>Test Infra>Client>ChromeOS
I'm not sure how to debug this. Please go ahead and open a b/ issue against GE; maybe they can find the issue from their side.
Status: WontFix (was: Untriaged)
WontFix as this is transferred to the GE component in b/ at https://b.corp.google.com/issues/114407451

Sign in to add a comment