-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
Only the logs and pages directories are generated in the locally persisted sitespeed-result/ directory at the end of the container run, with the other directory files missing #4262
Comments
Hi @taozhu520222 do you get any errors in the logs that you can share? |
There seems to be no such error in the past few days, I have currently accessed es,subsequently if there is a similar error, I will write the relevant files into the log to organize and send you, a million thanks for your prompt reply. |
Hi, I'm using sitespeed.io and once again only the logs and pages directories appear in the locally persistent sitespeed-result/ directory at the end of the container run, without generating the corresponding css, js, img directories and several .html files. The relevant files report the following error message: |
Cannot read properties of undefined (reading 'loaf') |
Your question
Hello, I'm having a problem with sitespeed.io, could you please could you explain it to me? A million thanks.
When I run 'docker run --rm -v /docker/sitespeed.io:/sitespeed.io sitespeedio/sitespeed.io -n 1 urls.txt', if the urls.txt contains around 100 url addresses, the In the locally persisted sitespeed-result/ directory at the end of the container run, only the logs and pages directories will appear, without the corresponding css, js, img directories and several other .html files. Is this caused by too many url addresses in the urls.txt file? Or is the file missing due to some URL access failure during the testing process? Because I subsequently reduced the number of addresses in urls.txt to 3~10, there is still a directory loss situation, observed the error message, only the URL test timeout, but there is no directory loss of abnormal error message.
The text was updated successfully, but these errors were encountered: