Skip to content

tests(lantern): remove Speedline from Lantern unit test for now#16060

Merged
connorjclark merged 2 commits intomainfrom
lantern-speed-index-input
Jun 11, 2024
Merged

tests(lantern): remove Speedline from Lantern unit test for now#16060
connorjclark merged 2 commits intomainfrom
lantern-speed-index-input

Conversation

@connorjclark
Copy link
Copy Markdown
Collaborator

ref #15841

Lantern expects to be given the result of running Speedline to determine SpeedIndex w/ optimistic mode. Ideally Lantern calls that library itself, but currently left to callers. Since there is no plan I'm aware of to include SpeedIndex in RPP, for now we can defer moving/using Speedline inside Lantern since only Lighthouse needs it. saves some work.

@connorjclark connorjclark requested a review from a team as a code owner June 10, 2024 23:01
@connorjclark connorjclark requested review from adamraine and removed request for a team June 10, 2024 23:01
const context = {computedCache: new Map()};
const data = await getComputationDataFromFixture({trace});
// TODO: observedSpeedIndex is from the Speedline library, and is used for optimistic
// mode. At the moment callers must pass the result into Lantern.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: what is the TODO here? Eventually move speedline inside the lantern library if we need it?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants