-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Firefox no longer connects to url #1454
Comments
We requested a trace level log when filing an issue, but the above is just an info level one. Please consult https://firefox-source-docs.mozilla.org/testing/geckodriver/geckodriver/TraceLogs.html in how to correctly record a trace log. |
My mistake
|
As you can see Firefox reached a neterror page with a connectionFailure message when Marionette requested a page load for |
It runs ok with Safari and Chrome. Is there anything I can check? |
I would suggest that you create a HTTP log while running your test. You would have to add two environment variables for the Firefox process. Details see https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging#Mac_OS_X. Note the files are huge, but compression should make it possible that you could upload one of those as attachment here. Or use other network sniffing tools like Wireshark. |
Apparently Wireshark is magical. I tried to record as per Mozilla, but it didn't work and locked up the port and rendered it useless. I rebooted my computer and ran my test. To my surprise it passed. So I tried the '--parallel' option and it sent me back to the error I had before. I recorded a failure (non-parallel) and decided to reboot again to record a success. After recording the success, I tried to get it to fail again, but I cannot get it to. I am attaching both files, but I guess the issue is resolved? |
Can you please explain what you mean with In regards of the logs... So yes, in case of failure the connection is always reset when the other end tries to send data to Firefox. You can see this by the RST flag in the response:
Firefox then tries again to re-create a connection but also that one is rejected. So there is clearly no problem with geckodriver here. But I'm not sure if Firefox misbehaves here, or if it is a combination with another tool on your system. If you have a firewall enabled try to disable it. Same for any AV software. Maybe this gives an indication. |
When you run tests with Django, you can run multiple tests at the same time with the --parallel flag python3 manage.py test python3 manage.py test --parallel I actually switched to Chrome as a result of this because it was testing 15-20 seconds faster than Firefox. |
Ok, thanks. So what happens when you reduce the number of parallel processes? Do you see the same problem when running even only on two cores? |
Well, once it failed(when it did fail) even running 1 single test would produce the same result. Both network trace files I submitted were of a single test, not with the |
Did you already follow my proposals from 2 days ago and tested with the Firewall and maybe other AV software disabled? Also when this problem happens can you reach the failed to load URL manually in a different instance of Firefox or another browser? Or use |
Well, I would have if it would still fail. But I did manage to create a new failure: python3 manage.py test --parallel It throws errors exactly where I canceled the test. I switched driver to Chrome, same thing. I restarted computer, same thing. New error:
I may have cancelled a test last time that started the other problem. |
That might be a problem with the test or the Selenium client. In such a case you are trying to use a session which hasn't been started yet. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue. |
I was using older versions of everything, then one day it didn't work. I installed all the latest and greatest, but nothing changed. If you need more, let me know.
System
Testcase
Stacktrace
Trace-level log
The text was updated successfully, but these errors were encountered: