-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this 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.'; |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
105f6b3
to
c9a4ef8
Compare
to make these more understandable: