New issue
Advanced search Search tips

Issue 669633 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression

Blocking:
issue 660868



Sign in to add a comment

telemetry_unittests on Windows-7-SP1 failing on chromium.win/Win7 Tests (dbg)(1)

Project Member Reported by iclell...@chromium.org, Nov 29 2016

Issue description

telemetry_unittests on Windows-7-SP1 failing on chromium.win/Win7 Tests (dbg)(1)

Type: build-failure

Builders failed on: 
- Win7 Tests (dbg)(1): 
  https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29


Roughly 148 tests are failing, I believe due to an unregistered crash key.

Reverting likely culprit: bf33256aee8db58c30b9d36e991055f2a4ed62a4
 
Labels: -Sheriff-Chromium
Owner: georgesak@chromium.org

Comment 2 by kbr@chromium.org, Nov 29 2016

Blocking: 660868
Labels: Pri-1 Type-Bug-Regression
This also caused failures of most of the GPU tests on the chromium.gpu.fyi waterfall. First failing build on one machine:
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20%28AMD%29/builds/352

Not sure how this made it through the CQ -- the GPU tests are run with dcheck_always_on=true -- or so I thought. win_chromium_rel_ng should have caught it.

Comment 3 by kbr@chromium.org, Nov 29 2016

Labels: Hotlist-PixelWrangler
This seems to fail only on debug bots, so maybe in release it doesn't reach DCHECK, that's why win_chromium_rel_ng didn't catch it, I think.
Status: Fixed (was: Assigned)
Closing this as my CL was reverted.

Sign in to add a comment