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

Issue 913598 link

Starred by 2 users
Status: Duplicate
Owner: ----
Closed: Dec 10
Cc:
szager@chromium.org
yhirano@chromium.org
█ ramyan@chromium.org
mamir@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

telemetry_perf_unittests time out on 'Linux Tests (dbg)' (64-bit)

Project Member Reported by hua...@chromium.org, Dec 10 
telemetry_perf_unittests has been timing out for a while.

https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29?limit=200

It's weird that the test (broken into 12 shards) does not name the test that times out?!  Manual bisection shows:
 Good: 76226 => https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/76226
 Bad:  76227 => https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/76227

Note that these timeout occur even for some runs that are labelled green.

The revision range in 76227 is:
  8b378f6dbff3509014d12fbac3cbda7fe064c5a1~..f31bdc3275791d3308f75cc90cd783246bc786c8

Comment 1 by hua...@chromium.org, Dec 10 

The specific tests that times out, based on comparing 76226 vs. 76227, are:

  core.stacktrace_unittest.TabStackTraceTest.testCrashMinimalSymbols 
  core.stacktrace_unittest.TabStackTraceTest.testCrashSymbols
  core.stacktrace_unittest.TabStackTraceTest.testValidDump

Comment 2 by szager@chromium.org, Dec 10 

Issue 913600 has been merged into this issue.

Comment 3 by bpastene@chromium.org, Dec 10

Mergedinto: 913070
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment