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

windows smoke test failing on dbw render-blocking-resources #12646

Open
paulirish opened this issue Jun 10, 2021 · 2 comments
Open

windows smoke test failing on dbw render-blocking-resources #12646

paulirish opened this issue Jun 10, 2021 · 2 comments
Assignees
Labels

Comments

@paulirish
Copy link
Member

It's been flaking/failing for a week or two.

@paulirish
Copy link
Member Author

Debugging this a bit between a passing run and a failing windows run.

I added some console logs to debug.

// passing
{
  estimateBeforeInline: 2319.4099999999994,
  estimateAfterInline: 1381.5499999999997,
  wastedMs: 938
}
// failing
 {
  estimateBeforeInline: 1076.71,
  estimateAfterInline: 1076.71,
  wastedMs: 0
 }

and what i'm seeing in the adjustedNodeTimings..

in the passing one:
  • document's duration is 756ms
  • the 3 cpu nodes have durations of 19-30ms
  • the remaining network nodes all have durations of 156ms.
in the failing one
  • document's duration is 752ms
  • the 3 cpu nodes have durations of 22-48ms
  • the remaining network nodes all have durations of 302ms.

diff for googlers: https://diff.googleplex.com/#key=u3j5ULSUx10p

so far that much doesnt mean much to me.. but making a record for now…

@patrickhulce
Copy link
Collaborator

this seems like a graph problem. we must be missing some information in the failing case that prevents it from being marked as necessary for FCP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants