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

Error running afterSession #396

Open
jholsgrove opened this issue Mar 22, 2018 · 0 comments
Open

Error running afterSession #396

jholsgrove opened this issue Mar 22, 2018 · 0 comments

Comments

@jholsgrove
Copy link

jholsgrove commented Mar 22, 2018

Grid Extras Version

v2.0.2
Selenium 3.11.0

Browser Version:

Chrome 65.0.3325.162
ChromeDriver 2.37

Expected Behavior -

Session exits and node is able to accept next forwarded test case

Actual Behavior -

Sessions stays, throwing this in the Hub log:

ERROR - Error running afterSession for ext. key a522d53972e493adbc5d07c56aebc49d, the test slot is now dead: null java.lang.NullPointerException at com.groupon.seleniumgridextras.grid.proxies.SetupTeardownProxy.getNodeExtrasPort(SetupTeardownProxy.java:313) at com.groupon.seleniumgridextras.grid.proxies.SetupTeardownProxy.afterSession(SetupTeardownProxy.java:147) at org.openqa.grid.internal.TestSlot.performAfterSessionEvent(TestSlot.java:253) at org.openqa.grid.internal.DefaultGridRegistry._release(DefaultGridRegistry.java:137) at org.openqa.grid.internal.DefaultGridRegistry.lambda$terminate$0(DefaultGridRegistry.java:122) at java.lang.Thread.run(Unknown Source)

Steps to reproduce -

Run a test via the grid with the node and hub being on Windows Server 2016.

One of my nodes runs on Server 2008 R2 and that manages to clean itself up nicely.

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

No branches or pull requests

1 participant