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

Issue 631922 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2016
Cc:
█ nduca@chromium.org
primiano@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

chrome://tracing broken

Project Member Reported by jochen@chromium.org, Jul 27 2016 
Chrome Version       : 54.0.2805.0
OS Version: 10.0
URLs (if applicable) : chrome://tracing

What steps will reproduce the problem?
1. go to chrome://tracing


What is the expected result?

Chrome tracing is there

What happens instead of that?

Uncaught ReferenceError: Polymer is not defined  tracing.js:707

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2805.0 Safari/537.36

Comment 1 by primiano@chromium.org, Jul 27 2016

Status: WontFix (was: Unconfirmed)
I filed https://github.com/catapult-project/catapult/issues/2550
but then I realized that is fixed in canary.

I can reproduce the same error by rolling back catapult at the version it was in 54.0.2805.0 (07aa51b63e8c0400) and confirm that is not there anymore in ToT today with catapult @ (48b4f78a291)

So don't think there is anything to do here, next canaries will be better.
On an unrelated note, would have been nice if the catapult autoroller did have some end-to-end tests, but that is tracked in
https://github.com/catapult-project/catapult/issues/2543

Comment 2 by primiano@chromium.org, Jul 27 2016 

Typo:
but then I realized that is fixed in s/canary/ToT/.
►

Sign in to add a comment