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

Issue 645118 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Jan 2017
Cc:
█ phajdan.jr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Analyze: OWNERS change triggered all unittests on linux_chromium_rel_ng

Project Member Reported by primiano@chromium.org, Sep 8 2016 
Change: https://codereview.chromium.org/2283703002/
touching only OWNERS file.

It did not land because the  linux_chromium_rel_ng  failed.
Turns out it did trigger all unittests there. Somehow analyze.py didn't work on that bot.
Weird because on all other bots the CL seems to have been a no-op as expected.

Comment 1 by tandrii@chromium.org, Sep 8 2016

Cc: phajdan.jr@chromium.org
Components: -Infra>CQ Infra>Client>Chrome
Pawel, maybe you can take a look?

Comment 2 by tandrii@chromium.org, Sep 8 2016

Summary: Analyze: OWNERS change triggered all unittests on linux_chromium_rel_ng (was: OWNERS change triggered all unittests on linux_chromium_rel_ng )

Comment 3 by phajdan.jr@chromium.org, Jan 5 2017

Mergedinto: 595176
Status: Duplicate (was: Unconfirmed)
Also see issue 663859 .
►

Sign in to add a comment