Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance error wording around busy traces. #2247

Merged
merged 2 commits into from
May 15, 2017
Merged

Conversation

paulirish
Copy link
Member

@paulirish paulirish commented May 13, 2017

to make these more understandable:

image

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

needs to update tests for identifying the culprit I think it looks for 'CPU' :)

@@ -26,7 +26,8 @@ const MIN_TASK_CLUSTER_PADDING = 1000;
const MIN_TASK_CLUSTER_FMP_DISTANCE = 5000;

const MAX_QUIET_WINDOW_SIZE = 5000;
const TRACE_BUSY_MSG = 'trace was busy the entire time';
const TRACE_BUSY_MSG = 'The main thread was busy for the entire trace recording. ' +
'First Interactive requires the main thread to reach a more idle state.';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: 'a more idle state' feels weird, can we say 'idle for several seconds' or something?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sgtm. done.

fixed tests too

@paulirish paulirish merged commit 7b86c71 into master May 15, 2017
@paulirish paulirish deleted the tracebusywording branch May 15, 2017 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants