New issue
Advanced search Search tips

Issue 755677 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Add a test for longtask reporting using |eval|

Project Member Reported by npm@chromium.org, Aug 15 2017

Issue description

Currently, all of the tests are using scripts. We should add a test that uses |eval|. This will help in determining the best way to find out how to get rid of noisy ExecutionContexts added set as |task_execution_context_| (or causing |task_has_multiple_contexts_| to be set to true) at PerformanceMonitor::Will(const probe::CallFunction& probe).

 
Owner: npm@chromium.org
Status: Assigned (was: Available)
Not high priority, but might as well leave this assigned to you.

Comment 2 by maxlg@chromium.org, Apr 23 2018

npm@, is there any update for this bug?

Comment 3 by npm@chromium.org, Apr 23 2018

Nope haven't got to it.
Status: WontFix (was: Assigned)
Evals are javascript so they go inside a script.

Sign in to add a comment