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

Update smokehouse audit/gathere config to speedup lighthouse #2732

Merged
merged 4 commits into from
Aug 14, 2017

Conversation

wardpeet
Copy link
Collaborator

First part of travis speedup. Smokehouse only uses audits that are necessary.

@wardpeet
Copy link
Collaborator Author

Quote from @brendankenny from the previous PR which I believe is a pretty good point. Any suggestions here?

we should designate at least one of these to run the default config (or full-config, now?) so that we're still smoke testing all of Lighthouse. Even if we don't assert all the results it means all potential files will be loaded and run, exposing at least some potential issues (even better if we do assert more results :)

We could make an explicit "default config" smoke test, but since the offline smoke test is already keeping most of the default config anyways, maybe that can be the one and we can just leave it on the default config?

Whichever one we run against the default config, we should probably leave a comment that it's intentionally running all of it so future refactors

module.exports = {
extends: 'lighthouse:default',
settings: {
onlyAudits: [
Copy link
Collaborator

Choose a reason for hiding this comment

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

could we do onlyCategory best-practices or does that push the number of passes up?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

did a few runs and almost no runs, It's about 2-3 audits more which don't do much

@patrickhulce
Copy link
Collaborator

re: brendan's comments, let's take the one that already takes the longest/has to do the most passes and make that run the default config :)

@wardpeet
Copy link
Collaborator Author

I updated the tricky ttci test As it only runs one site & takes quite some time already.
DBW is taking the longest but also runs more than 1 page.

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.

great stuff @wardpeet!

Just weigh in on the one comment and I think we can land

* Config file for running PWA smokehouse audits.
*/
module.exports = {
extends: 'lighthouse:default',
Copy link
Member

Choose a reason for hiding this comment

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

just remove this file and run the default in tricky-ttci/run-tests.sh? Unless you think it's better if it has its own file for future changes or whatever

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

nah doesn't matter, we can just extend it again when we need it.

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!

@brendankenny
Copy link
Member

🏇 🏎 ⏱

@brendankenny brendankenny merged commit e72483b into GoogleChrome:master Aug 14, 2017
@wardpeet wardpeet deleted the travis/smokehouse-speedup branch November 8, 2019 23:29
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.

3 participants