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

Issue 660027 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug

Blocking:
issue 628752



Sign in to add a comment

security_SandboxStatus fails in multiple canaries

Reported by jrbarnette@chromium.org, Oct 27 2016

Issue description

This is the human-friendly version of auto-filed bug 628752.

The security_SandboxStatus test is failing in multiple canaries,
starting with R56-8937.0.0.

Here's the relevant blamelist:
    https://crosland.corp.google.com/log/8936.0.0..8937.0.0

The change started failing without warning in the CQ with
this run:
    https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/12721

Generally, the CQ has been failing ever since.
 
Cc: mka@chromium.org
Components: -OS>Systems UI
Owner: x...@chromium.org
The PFQ is stupidly green.  That means we have a coverage problem
in the PFQ.  It also means a Chrome bug that escaped the PFQ is a
likely culprit.  Adding fuel to that fire, the last passing canary
used Chrome 56.0.2900.0; the first failing canary used 56.0.2901.0.

Reassigning to the Chrome gardener.

Mergedinto: 659894
Status: Duplicate (was: Assigned)
... I see I should read the tree status.

Sign in to add a comment