-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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: remove estimated-input-latency and first-cpu-idle #12553
Conversation
'first-cpu-idle': { | ||
numericValue: '>2000', | ||
}, | ||
// TODO: ? |
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.
Should I replace these smoke expectations with something else?
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.
nah. FCI is basically TTI and TTI is already there.
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.
delete?
what happened to |
I started just removing the EIL/FCI references then decided to just strip the entire thing but what is needed for treemap |
could you split that and we could just land that quickly independently of other changes? e.g. I updated individual lines in |
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.
a few more things you'll see if you search FCPUI
.
- There's a few errors that appear to be safe to delete. (they were never in the proto
- And there's a block in
lantern-baseline-accuracy.json
that you'll need to delete.
(and the devtools tests need a rebaseline)
'first-cpu-idle': { | ||
numericValue: '>2000', | ||
}, | ||
// TODO: ? |
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.
nah. FCI is basically TTI and TTI is already there.
'first-cpu-idle': { | ||
score: '>=0.90', // primarily just making sure it didn't fail/go crazy, specific value isn't that important | ||
}, | ||
// TODO ? |
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.
flagging to remove
@@ -17,10 +17,11 @@ module.exports = [ | |||
requestedUrl: 'http://localhost:10200/tricky-tti.html', | |||
finalUrl: 'http://localhost:10200/tricky-tti.html', | |||
audits: { | |||
'first-cpu-idle': { |
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.
on these you could add assertions for TBT if you want, but i don't think that's necessary or a great test for that metric.
so i'm +1 on removing in this file too
@paulirish has got this one under control 👍 |
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.
one last TODO to remove and looks like need to run yarn update:test-devtools
one more time, but otherwise looks good to ship
nice work in all of those (many) test files
'first-cpu-idle': { | ||
numericValue: '>2000', | ||
}, | ||
// TODO: ? |
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.
delete?
assert.equal(EstimatedInputLatency.calculateRollingWindowEIL(events), 4516); | ||
}); | ||
|
||
it('handles continuous tasks', async () => { |
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.
good stuff in here. Oh well :)
ref #11866