1) a handful of test failures were from node.record instead of node.request
2) missed passing networkRecords to createTestTrace
3) fixed difference re: requests from Fetch
4) fixed difference re: data urls not having a resource size
5) handle creating requests in a redirect chain better
6) createTestTrace was putting initiator data on wrong event
7) always produce network events in createTestTrace (since it impacts graph construction when doing cpu node linking)
1) a handful of test failures were from
node.record
instead ofnode.request
2) missed passing networkRecords to createTestTrace 3) fixed difference re: requests from Fetch 4) fixed difference re: data urls not having a resource size 5) handle creating requests in a redirect chain better 6) createTestTrace was putting initiator data on wrong event 7) always produce network events in createTestTrace (since it impacts graph construction when doing cpu node linking)ref https://github.com/GoogleChrome/lighthouse/issues/15841