Invalid session id errors when running examples #207
Comments
|
Hi, I cannot reproduce this on Windows 10 or Ubuntu. Also all examples are running as part of CI build so something should be with your machine. Please try to dig into the root cause of the issue. Windows 10 output: Ubuntu output: |
|
Are you getting this error message? https://travis-ci.org/mucsi96/nightwatch-api/jobs/494760085#L680 The error message is really strange as it was running perfectly before updating the geckodriver to latest even the test are not running against firefox, but against headless chrome. Interesting .... Can you try to switch to earlier version of geckodriver or remove it completely? What version of Node and NPM you are using? |
|
mint@mint-HP-ProBook-4520s ~ $ node --version Is there some other system I need to be running in the background, like selenium server or whatever? |
|
Hi @mucsi96 and @marcdonovan , there was an issue with geckodriver webdriverio-community/node-geckodriver#59. It is fixed in 1.15.1 |
|
I assume the issue is resolved. Closing... Feel free to reopen if it still exist. |
|
Removed geckodriver, still the same errors Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id |
|
I'm not allowed to reopen the issue. I will try this on vanilla ubuntu on amazon |
|
ssh -i .ssh/cucumber.pem [email protected] mint@mint-HP-ProBook-4520s ~ $ cat .ssh/cucumber.pem ubuntu@ip-172-31-26-199:~/nightwatch-api/packages/cucumber-example$ npm run test
Feature: DuckDuckGo Scenario: Searching DuckDuckGo Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id ✖ Testing if the page title equals "DuckDuckGo — Privacy, simplified." in 1000 ms. - expected "DuckDuckGo — Privacy, simplified." but got: "[object Object]" Scenario: Searching DuckDuckGo again Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id ✖ Testing if the page title equals "DuckDuckGo — Privacy, simplified." in 1000 ms. - expected "DuckDuckGo — Privacy, simplified." but got: "[object Object]" Feature: Google Search Scenario: Searching Google Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id ✖ Testing if the page title equals "Google" in 1000 ms. - expected "Google" but got: "[object Object]" Scenario: Searching Google again Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id Error while running .getPageTitle() protocol action: invalid session id ✖ Testing if the page title equals "Google" in 1000 ms. - expected "Google" but got: "[object Object]" Failures:
4 scenarios (4 failed) npm ERR! A complete log of this run can be found in: |
|
It's not my box. You have root so debug away. |
|
As we are not able to reproduce https://travis-ci.org/mucsi96/nightwatch-api/builds/495773793?utm_source=github_status&utm_medium=notification please try the same test with pure NightwatchJS without using this package. That would at least show where is the problem |
|
I just put up a virgin VM on AWS that reproduces the problem and I gave you root access to try it out. How are you not able to reproduce? What is pure Nightwatchjs? What package are you wanting me to without using? I tried removing gecko and same. All I did on the virgin VM was install latest nodejs, checkout your github, run test and it failed. |
|
Do you have Chrome installed on this VM? The cucumber example is configured to run on headless Chrome browser by default. Also you should turn on the WebDriver logs to see better what’s the issue here |
|
I don’t really like the manner you communicate and expect us to fix an issue submitted only by you. For some reason nobody else is complaining about this. Also please don’t forget this is an open-source project created and maintained in free time. No one is paying us to do that. We are able to exist only by contribution of people willing to help the community. We try to prioritize our efforts on issues which affect more people first |
|
I am paying Amazon to demo the error. You know what, I'm out with this project. I thought it had promise but I can't get it to work following your instructions. I've been a coder for 40 years and I'm done with you. |
|
Instance terminated. Nevermind. |
|
Dear Mr @marcdonovan , I am sorry that you are facing issue with this package. With due respect, kindly be a little polite in your conversation. Reiterating what has been said already, this is an open source project and an issue wont be fixed/addressed just because it is posted. I regret to know that you had to pay Amazon. But that is how it works. If you still think there is some issue, feel free to fix and raise a PR with your 40yrs of coding experience. We will be glad to merge it and add you as contributor. Thank you for the support and understanding. |
|
FYI I've linked to another example of this occurring above, I also have a hunch that this issue might actually be the result of a nightwatch issue: nightwatchjs/nightwatch#1936 if anyone encounters this and can reproduce consistently, please add more info there (and upvote the issue) |
Expected Behavior
Expect example tests to run without errors
Current Behavior
Feature: Google Search
Scenario: Searching Google
Given I open Google`s search page
Error while running .navigateTo() protocol action: invalid session id
Steps to Reproduce (for bugs)
git clone https://github.com/mucsi96/nightwatch-api.git
cd nightwatch-api/packages/cucumber-example
npm install
npm run test
Your Environment
Linux mint
The text was updated successfully, but these errors were encountered: