You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue with LambdaTest tunnel which gets timed out in polling mode through Jenkins due to different tunnel ready message with geb-lambdatest plugin when tunnel is started in polling mode instead of websocket mode. We have modified the tunnel ready message. This will fix the lambdatest tunnel getting started with Jenkins . We need your help @erdi in committing it. Pull Request
final String tunnelReadyMessage = 'Tunnel claim successful'
to final String tunnelReadyMessage = 'Secure connection established, you may start your tests now'
The text was updated successfully, but these errors were encountered:
ArpitLT
changed the title
Update the message searched for in LambdaTest tunnel process output…
LambdaTest tunnel has now a different tunnel ready message
Mar 22, 2020
Hi @erdi ,
Hope you're all well and safe in this Covid-19 outbreak. The LambdaTest tunnel can work in two modes: websocket and polling mode. However, in both modes, tunnelReady messages are different which caused problems when the tunnel is started in polling mode. This makes the plugin timeout as it doesn't find the exact text when tunnel starts in polling mode (with nows argument).
To resolve this issue, we'd like you to update tunnelReadyMessage for which we've raised a pull request as well:
final String tunnelReadyMessage = 'Tunnel claim successful'
to final String tunnelReadyMessage = 'Secure connection established, you may start your tests now'
There is an issue with LambdaTest tunnel which gets timed out in polling mode through Jenkins due to different tunnel ready message with geb-lambdatest plugin when tunnel is started in polling mode instead of websocket mode. We have modified the tunnel ready message. This will fix the lambdatest tunnel getting started with Jenkins . We need your help @erdi in committing it.
Pull Request
final String tunnelReadyMessage = 'Tunnel claim successful'
to
final String tunnelReadyMessage = 'Secure connection established, you may start your tests now'
The text was updated successfully, but these errors were encountered: