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

tests: reduce expected value of render-blocking-requests smoke #16011

Merged
merged 2 commits into from
May 21, 2024

Conversation

connorjclark
Copy link
Collaborator

@connorjclark connorjclark commented May 21, 2024

This test has started to consistently return values between 90-100 in CI, so lets lower it.

I investigated a bit, and something that sticks out is that wastedMs (aka download time, according to the comment) being used here did not match the ?delay param at all. This is after simulating the fcp graph, but I'd expect the download times to be longer not shorter. The headers start timing on the trace event contains the delay as expected, so perhaps we are building the lantern graph incorrectly.

debug the artifacts yourself - the http://localhost:10200/dobetterweb/dbw_tester.css?delay=2200 is one request that has a wastedMs of much less than its delay:

https://github.com/GoogleChrome/lighthouse/actions/runs/9169845726/artifacts/1522909511

node cli "-A=/Users/cjamcl/Downloads/Smokehouse (ubuntu; chrome ToT)/2/dbw" http://localhost:10200/dobetterweb/dbw_tester.html

@connorjclark connorjclark requested a review from a team as a code owner May 21, 2024 19:09
@connorjclark connorjclark requested review from adamraine and removed request for a team May 21, 2024 19:09
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