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

Issue 633579 link

Starred by 2 users
Status: WontFix
Owner:
█ nduca@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Cc:
caseq@chromium.org
gab@chromium.org
█ nduca@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

testBasicTraceRecording failing on Mac 10.10

Project Member Reported by nedngu...@google.com, Aug 2 2016 
Log:
  *************** BROWSER STANDARD OUTPUT ***************
  2016-07-27 11:14:04.608 Chromium[6176:41586] NSWindow warning: adding an
unknown subview: <FullSizeContentView: 0x7f9165047eb0>
  2016-07-27 11:14:04.608 Chromium[6176:41586] Call stack:
  (
      "+callStackSymbols disabled for performance reasons"
  )
  [6176:1299:0727/111407:ERROR:CONSOLE(2054)] "Error: Could not find an importer
for the provided eventData.
      at Import.createImports (chrome://tracing/tracing.js:1457:64)
      at Task.run (chrome://tracing/tracing.js:2042:13)
      at runAnother (chrome://tracing/tracing.js:2054:136)
      at runTask (chrome://tracing/tracing.js:2017:57)
      at processIdleWork (chrome://tracing/tracing.js:2023:116)
      at window.requestIdleCallback.timeout
(chrome://tracing/tracing.js:2011:81)", source: chrome://tracing/tracing.js


(https://build.chromium.org/p/chromium.mac/builders/Mac10.10%20Tests/builds/7719/steps/telemetry_perf_unittests/logs/stdio)

Comment 1 by nedngu...@google.com, Aug 2 2016

Cc: -gab@chromium.org nduca@chromium.org
Labels: -Pri-3 Pri-1

Comment 2 by nedngu...@google.com, Aug 2 2016

Cc: gab@chromium.org

Comment 3 by nedngu...@google.com, Aug 2 2016

Cc: caseq@chromium.org
Looks like this is a flaky failure.

First failed build is in https://build.chromium.org/p/chromium.mac/builders/Mac10.10%20Tests/builds/7671

Comment 4 by nedngu...@google.com, Aug 2 2016

Owner: nduca@chromium.org
Assign to Nat for triaging.
Project Member

Comment 5 by bugdroid1@chromium.org, Aug 2 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ff4ed9af692f5d0d79654a81adf4fd82b500a107

commit ff4ed9af692f5d0d79654a81adf4fd82b500a107
Author: nednguyen <nednguyen@google.com>
Date: Tue Aug 02 15:23:45 2016

[tools/perf] Disable testBasicTraceRecording on Mac

BUG= 633579 
TBR=nduca@chromium.org, gab@chromium.org

Review-Url: https://codereview.chromium.org/2206433003
Cr-Commit-Position: refs/heads/master@{#409195}

[modify] https://crrev.com/ff4ed9af692f5d0d79654a81adf4fd82b500a107/tools/perf/core/about_tracing_integration_test.py

Comment 6 by gab@chromium.org, Aug 2 2016 

 Issue 633361  has been merged into this issue.
Project Member

Comment 7 by chromium...@appspot.gserviceaccount.com, Aug 2 2016 

Detected 5 new flakes for test/step "telemetry_perf_unittests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMAsSBUZsYWtlIiV0ZWxlbWV0cnlfcGVyZl91bml0dGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app.

Comment 8 by caseq@chromium.org, Aug 2 2016 

This goes through webui bindings to tracing controller and JSONTraceDataSink+CompressedTraceDataEndpoint, not through inspector, right?

Also, can we get actual failure log? The one bug points to has just core.minidump_unittest.BrowserMinidumpTest.testMultipleCrashMinidumps failing and testBasicTraceRecording is fine there.

Comment 10 by nedngu...@google.com, Aug 2 2016

Status: WontFix (was: Untriaged)
Actually I think the sherrif mistaken this as the reason causing telemetry_perf_unittest is failed. ( issue 633761 )

This should already be fixed in  issue 630030 . I will revert the disabling CL.
Project Member

Comment 11 by bugdroid1@chromium.org, Aug 2 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/539e1fedbe28dc6262cb877138e58ec00b958319

commit 539e1fedbe28dc6262cb877138e58ec00b958319
Author: nednguyen <nednguyen@google.com>
Date: Tue Aug 02 23:13:25 2016

Revert of [tools/perf] Disable testBasicTraceRecording on Mac (patchset #1 id:1 of https://codereview.chromium.org/2206433003/ )

Reason for revert:
This test is not the cause of telemetry_perf_unittest flakiness.

Original issue's description:
> [tools/perf] Disable testBasicTraceRecording on Mac
>
> BUG= 633579 
> TBR=nduca@chromium.org, gab@chromium.org
>
> Committed: https://crrev.com/ff4ed9af692f5d0d79654a81adf4fd82b500a107
> Cr-Commit-Position: refs/heads/master@{#409195}

TBR=
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= 633579 

Review-Url: https://codereview.chromium.org/2208563002
Cr-Commit-Position: refs/heads/master@{#409373}

[modify] https://crrev.com/539e1fedbe28dc6262cb877138e58ec00b958319/tools/perf/core/about_tracing_integration_test.py
►

Sign in to add a comment