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

sitespeed.io latest docker image timeout issue with javascript #4017

Closed
dpeddaswamy opened this issue Nov 29, 2023 · 7 comments
Closed

sitespeed.io latest docker image timeout issue with javascript #4017

dpeddaswamy opened this issue Nov 29, 2023 · 7 comments

Comments

@dpeddaswamy
Copy link

Your question

Hi Team,
i am executing sitespeed.io test using docker image from github actions. i have configured java script file and giving input to docker image. But when i execute the test i m getting timeout error.

Command: docker run --rm -v $(pwd):$(pwd) -w $(pwd) sitespeedio/sitespeed.io -n 1 --spa --multi TestPlans/testscript.js -b edge --cookie TEXT="$COOKIE" --browsertime.video false --axe.enable --chrome.timeline --config TestPlans/PageSummaryConfig.json --outputFolder ./sitespeed-result

Log:
[2023-11-29 14:48:25] INFO: Versions OS: linux 5.19.0-41-generic nodejs: v20.9.0 sitespeed.io: 30.6.0 browsertime: 19.1.0 coach: 8.0.2
[2023-11-29 14:48:25] INFO: Axe version 4.8.2 plugin activated
[2023-11-29 14:48:25] INFO: Running tests using Edge - 1 iteration(s)
[2023-11-29 14:48:25] INFO: Using Edge is experimental at the moment and use the same configuration as for Chrome
[2023-11-29 14:48:30] INFO: Start to measure priceDateRule
[2023-11-29 14:48:31] INFO: Navigating to url https://<testdomain.com> iteration 1
[2023-11-29 14:50:42] ERROR: Failed waiting on page to finished loading, timed out after 120000 ms Error: Running page complete check
return (function(waitTime) {
const timing = window.performance.timing;
const p = window.performance;
const resourceTimings = p.getEntriesByType('resource');
if (resourceTimings.length > 0) {
const lastEntry = resourceTimings.pop();
const stop = p.now() - lastEntry.responseEnd > waitTime;
if (stop) {
// empty resource timings for the next run
p.clearResourceTimings();
return true;
}
}
else return false;

But when i save all urls in notepad file and execute the docker image , its working as expected..
Command: docker run --rm -v $(pwd):$(pwd) -w $(pwd) /sitespeedio/sitespeed.io -n 1 --spa TestPlans/Test_URLs.txt --cookie TEXT="$COOKIE" --browsertime.video false --axe.enable --chrome.timeline --config TestPlans/PageSummaryConfig.json --outputFolder ./sitespeed-result

could you please help in resolving the issue.

@soulgalore
Copy link
Member

Hi @dpeddaswamy can you test that the GitHub action can access the URL? You can try with curl or something like that first.

@dpeddaswamy
Copy link
Author

Hi @soulgalore, i tried curl command with Proxy and without proxy, its successfully redirecting to login page. But failing with timeout issue.
image

image

@dpeddaswamy
Copy link
Author

and sometimes i m getting SSL Connection timeout error. Not sure if this is Github runner issue.
image

@soulgalore
Copy link
Member

If you run it locally on your machine, does it work flawlessly? I remember when I tried it before GitHub runners had low resources cpu/memory and broke some tests for me when I tried it out. But I haven't been using it much nowadays.

@soulgalore
Copy link
Member

Didn't get any response so closing.

@dpeddaswamy
Copy link
Author

@soulgalore, above issue was fixed after adding Host entry in GitHub workflow yml file.

However, from Last month, i am facing again same issues with latest sitespeed.io docker image. Even after adding host entry i m getting time out error. Each url is tried 5 times. in between some times it works for first time, or at 3rd time etc..

Could you please help.

@soulgalore
Copy link
Member

I wonder then if GitHub changed anything? I would add curl to the action and try how that works.

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

No branches or pull requests

2 participants