Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
HTML report erroring out frequently with --chrome.timeline flag #2310
I'm noticing that the HTML reports errors out frequently with the following error:
I'm running this command (modified the path and website for example):
I've not figured out why. It could be a memory issue or some race condition.
Hi @gidztech I'll push just a guard to make sure it doesn't fail but it is something else that's the root of the problem.
I run the same for the setup used here: https://dashboard.sitespeed.io/d/000000044/page-timing-metrics?orgId=1&var-base=sitespeed_io&var-path=desktopLoggedIn&var-group=en_wikipedia_org&var-page=_wiki_Barack_Obama&var-browser=chrome&var-connectivity=cable&var-function=median where I login the user and then test a couple of pages + collect the chrome timeline data.
Either there's a specific problem with how we use the --preScript or it's something with a combination of the preScript and the page you test. Any chance you could share that with me (peter [AT] soul galore [dot] com) then I can better get an understanding.
One thing I would look at first would to verify that the page finished loading in your preScript where you login the user (like if there's a redirect or something like that).
Hi @soulgalore. Just got around to looking at this again. Been a busy few weeks.
Thanks for adding the guard. It no longer errors out. However, when I download the Timeline, the data inside the file is not valid JSON. It's a load of random encodings by the looks of it.
The rest of the report looks fine. I can see the page rendered correctly, the video and filmstrip look correct to, so I can't see any reason why the login script is at fault. All it does is navigate the page, input some username and password, click submit, and wait for a selector.
Aha, interesting, looks like an upstream bug then, either in Chrome or Chromedriver. I've seen that we sometimes on dashboard.sitespeed.io also gets problems getting the trace log but I haven't actually looked into the actual log. I've check next time it happens and if it is the same I'll create an Chromedriver bug and ask for help.