-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Web crawler randomly fails on some manual test on CI #14906
Comments
I checked the browser version and launch arguments on CI and on my local environment: Local environment
CI environment
There is no difference between local and CI environments, except the path to the executable and the |
All debugging I'm doing on |
IdeaSwitching to the new headless mode in Puppeteer ( ResultChrome doesn't seem to start at all. In console I see only two lines: "🔎 Starting the Crawler" and then "✨ No errors have been found.". The execution time of the crawler script is ~1 second. |
IdeaBumping Puppeteer to the latest version v21.1.1. ResultSame as above: Chrome doesn't seem to start at all. |
IdeaEnabling debug mode in Puppeteer v21.1.1 by providing ResultThere are some errors that does not tell much about how to fix them:
|
IdeaInstalling some dependencies that might be needed on Linux machine, as described on https://pptr.dev/troubleshooting#running-puppeteer-on-circleci. Still using Puppeteer v21.1.1. ResultSame as above: Chrome doesn't seem to start at all. |
IdeaMaybe manually starting the dbus service could help? ResultSame as above: Chrome doesn't seem to start at all. |
It seems that after using the latest Puppeteer, the It seems that the issue with
It seems that the request to the Attached a log from the Puppeteer when the |
I tried detecting if the frame navigation was performed: await Promise.all(
page.mainFrame().childFrames().map( frame => {
return frame.waitForNavigation();
} )
); but the promise is not resolved for the Also, I experimented with many chrome flags but without success. For now, no idea how to fix this issue. |
This issue is not reproducible in a non-headless mode locally. But on CI the error occurs in both headless modes (new and old ones) and in a non-headless mode. |
I was able to create a minimal reproducible example. It looks like that this is an issue either in Puppeteer or Chrome. |
There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the solution, leave a comment or reaction under this issue. |
We've closed your issue due to inactivity. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it). |
📝 Provide detailed reproduction steps (if any)
Recently, there have been a lot of reports from a web crawler that one test fails on CI:
I'm not able to reproduce this error locally.
✔️ Expected result
The
noselection-iframe
manual test does not fail in web crawler.❌ Actual result
The
noselection-iframe
manual test fails randomly in web crawler. After restarting the job on CI the test passes.❓ Possible solution
Check the exact version of Chrome that is run on CI and its arguments. Maybe there is a difference between CI and local environment?
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
The text was updated successfully, but these errors were encountered: