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

The 'get' timeouts command is failing when using Selenium Server #8800

Closed
kretschmannj opened this issue Oct 16, 2020 · 3 comments
Closed

The 'get' timeouts command is failing when using Selenium Server #8800

kretschmannj opened this issue Oct 16, 2020 · 3 comments

Comments

@kretschmannj
Copy link

kretschmannj commented Oct 16, 2020

🐛 Bug Report

Attempting to get the current timeout values is failing using seleniumServer. I'm running a Nightwatch test with the command 'this.timeouts((result) => { console.log('timeouts:', result) })'. In the verbose output I see this ...

 → Running command: timeouts ([Function])
   Request GET  /wd/hub/session/010f6e32-51c9-4509-89d0-fece900d2679/timeouts  
   Response 500 GET /wd/hub/session/010f6e32-51c9-4509-89d0-fece900d2679/timeouts (7ms)
   {
     value: {
       stacktrace: '',
       message: 'GET /session/010f6e32-51c9-4509-89d0-fece900d2679/timeouts\n' +
         "Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'\n" +
         "System info: host: 'CA01000JWL2P13L', ip: '10.17.242.242', os.name: 'Windows 10', os.arch: 'x86', os.version: '10.0', java.version: '1.8.0_201'\n" +
         'Driver info: driver.version: unknown',
       error: 'unknown command'
     },
     status: 9
}
 Error while running .getTimeouts() protocol action: unknown command – GET /session/010f6e32-51c9-4509-89d0-fece900d2679/timeouts

timeouts: {
  status: -1,
  code: '',
  state: '',
  value: {
    stacktrace: '',
    message: 'GET /session/010f6e32-51c9-4509-89d0-fece900d2679/timeouts\n' +
      "Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'\n" +
      "System info: host: 'CA01000JWL2P13L', ip: '10.17.242.242', os.name: 'Windows 10', os.arch: 'x86', os.version: '10.0', java.version: '1.8.0_201'\n" +
      'Driver info: driver.version: unknown',
    error: 'unknown command'
  },
  errorStatus: 9,
  error: 'unknown command – GET /session/010f6e32-51c9-4509-89d0-fece900d2679/timeouts',
  httpStatusCode: 500
}
  → Completed command: timeouts ([Function]) (30ms)

I only have this issue when I use the standalone selenium server ...

firefox_selenium: {
   selenium: {
     start_process: true,
     port: 5555,
     server_path: "node_modules/selenium-server/lib/runner/selenium-server-standalone-3.141.59.jar"
   },
   desiredCapabilities: {
     browserName: 'firefox',
     acceptInsecureCerts: true
   }
 },

I have no such issue when I use webdriver/geckodriver ...

    firefox_webdriver: {
      webdriver: {
        start_process: true,
        server_path: 'node_modules/geckodriver/geckodriver.exe'
      },
      desiredCapabilities: {
        browserName: 'firefox',
        alwaysMatch: {
          acceptInsecureCerts: true // doesn't work in Jenkins
        },
      }
    },

Environment

OS: Windows 10
Browser: Chrome or Firefox (fails in both)
Browser version: Chrome 85 / Firefox 81.0.2
Browser Driver version: ChromeDriver 85.0.4183.87 / GeckoDriver 0.27.0
Nightwatch version: 1.4.2

@ghost ghost added the needs-triaging label Oct 16, 2020
@kretschmannj kretschmannj changed the title The 'get' timeouts command is failing in Firefox with Selenium Server The 'get' timeouts command is failing when using Selenium Server Oct 16, 2020
@pujagani
Copy link
Contributor

With the lastest version, both http://localhost:4444/wd/hub/session/<session-id>/timeouts and http://localhost:4444/session/2407738ef8bfb7a0a74dcbe6f962858c/<session-id>/timeouts in the Standalone mode.

@pujagani
Copy link
Contributor

The above mentions URLs are working with ChromeDriver and GeckoDriver.

@diemol
Copy link
Member

diemol commented Dec 23, 2020

Thanks for troubleshooting, @pujagani

Those commands are failing for Grid 3.141.59, but if you try the new Grid 4 (currently at Alpha 7 and soon Beta 1), they will work, as pointed out above.

Closing this issue as it is working on the new Grid 4.

@diemol diemol closed this as completed Dec 23, 2020
@diemol diemol reopened this Dec 23, 2020
@diemol diemol closed this as completed Dec 23, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Sep 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants