[go: nahoru, domu]

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

misc(lantern-collect): drop sampling #15072

Merged
merged 3 commits into from
May 24, 2023
Merged

Conversation

connorjclark
Copy link
Collaborator

When we next update the lantern test database, we don't want to do any sampling. Simpler to run ~10x the amount of URLs and just drop whatever runs happened to flake even once.

Much of the complexity of this collection script came from the sampling, so it's nice to be rid of that.

No longer need two archives.

Added a "retries" property - if something was retried, it won't show in the "golden" file. Can still be found in the "summary" file (also their traces are still in the zip) for purposes of future analysis (could be interesting to see how lantern does with URLs that LH tends to fail on?)

@connorjclark connorjclark requested a review from a team as a code owner May 12, 2023 02:06
@connorjclark connorjclark requested review from adamraine and removed request for a team May 12, 2023 02:06
/** @typedef {Result & {metrics: LH.Artifacts.TimingSummary}} ResultWithMetrics */
/** @typedef {{results: ResultsForUrl[], warnings: string[]}} Summary */
/** @typedef {{results: ResultsForUrl[]}} Summary */
/** @typedef {import('../run-on-all-assets.js').Golden} Golden */
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Reminder that the Summary and all types in collect/ can change without implication for the lantern baseline testing code - as long as we continue to target the Golden output format.

* @param {string} message
*/
function warn(message) {
summary.warnings.push(message);
Copy link
Collaborator Author
@connorjclark connorjclark May 12, 2023

Choose a reason for hiding this comment

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

co-locating these with the url run result is way more useful.

@@ -16,14 +17,13 @@ import fetch from 'node-fetch';
import defaultTestUrls from './urls.js';
import * as common from './common.js';
import {LH_ROOT} from '../../../../root.js';
import {makeGolden} from './golden.js';
Copy link
Member

Choose a reason for hiding this comment

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

golden.js only has this function, could we move it in here?

Also, WDYT about renaming the function to makeUrlSummary or something since the "golden" part refers to it taking the median of the samples, and this no longer happens.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Many things inside of scripts/lantern refer to this thing as golden, and I don't want to propagate that change everywhere for this PR.

@devtools-bot devtools-bot merged commit 469157a into main May 24, 2023
33 checks passed
@devtools-bot devtools-bot deleted the lantern-collect-no-sample branch May 24, 2023 21:42
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.

None yet

3 participants