Open yashgarde opened 1 month ago
Hi @yashgarde sorry I missed this issue during my vacation. So the case with the range error must mean that the server returns a broken timing for a request. Let me add a fix for that this weekend so it just swallows the error.
For fullyLoaded metric to URL undefined I've done a couple of changes the last months to better catch that, not sure it catches everything though.
Your question
Opening this issue as requested in #4124 regarding the RangeError I am experiencing.
Upon further testing, this issue is not occurring consistently and is not limited to tests with multiple iterations. Even with a single iteration of the test, there are cases when the test completes successfully and cases when this RangeError occurs.
Case 1: Test completes successfully (errors in log)
In this case, a chrome trace log is generated but all the result HTML and final output seems correct.
Case 2: Test fails with RangeError, no trace log generated
This test does not generate the
chromePerflog.json.gz
file at all within the results.Both tests were run through the Onlinetest testing framework for sitespeed.io with the exact same command-line options and
--browsertime.chrome.collectPerfLog true
set for both cases to generate chrome perf logs.