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

core(metrics): move first-interactive to first-cpu-idle #4982

Merged
merged 4 commits into from
Apr 19, 2018
Merged

Conversation

patrickhulce
Copy link
Collaborator

@patrickhulce patrickhulce commented Apr 17, 2018

  1. Renames first-interactive to first-cpu-idle according to the new metric name
  2. Moves core first-interactive computed artifact to a metric computed artifact

This is blocked on #4981 since that PR moves away from using first CPU idle for load-fast-4-pwa

}
},
"rawValue": 4927.278,
"debugString": "First Interactive was 4,930 ms. More details in the \"Performance\" section.",
Copy link
Member

Choose a reason for hiding this comment

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

since this is dependent on the other PR, shouldn't this be passing?

also the text still says "first interactive". looks like you need to updatejson, eh

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yeah yeah need to update the JSON it was based on my branch before I updated the json there

@patrickhulce patrickhulce changed the title core(metrics): move first-interactive first-cpu-idle core(metrics): move first-interactive to first-cpu-idle Apr 18, 2018
@patrickhulce patrickhulce changed the base branch from load_fast_4_pwa_lantern to master April 18, 2018 21:06
@GoogleChrome GoogleChrome deleted a comment from googlebot Apr 18, 2018
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.

LGTM

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.

4 participants