-
-
Notifications
You must be signed in to change notification settings - Fork 761
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
org.openqa.selenium.remote.ProtocolHandshake createSession messages logging as errors #603
Comments
@Brian-Watson there is conflict in dependencies . Can you pls share the logs n pom.xml as gist |
@saikrishna321 Sure. I am currently using gradle for my dependencies, so my build.gradle file just includes...
Which logs would you be interested in? |
@Brian-Watson can you try with
|
@Brian-Watson |
@Brian-Watson I am closing this issue. 5.0.0-BETA6 was published. Please try it. If not everything is ok then please re-open this issue. |
@saikrishna321 @TikhomirovSergey Just wanted to update you guys to say I installed the latest BETA6 and it indeed fixed my issue. Thank you guys so much for your work!!!! |
Description
After just recently upgrading to java-client 5.0.0-BETA4, my Appium jenkins jobs are now ending as failure even though all tests pass.
Environment
Details
Each time I create a new IOSDriver or AndroidDriver, I see the following in my jenkins job console output...
com.company.dtr.brokeragent.TransactionRoomsDetailsTestSuite_BA > addTransactionContactDetailsFromNetwork STANDARD_ERROR Mar 15, 2017 5:13:23 PM org.openqa.selenium.remote.ProtocolHandshake createSession INFO: Attempting bi-dialect session, assuming Postel's Law holds true on the remote end Mar 15, 2017 5:13:29 PM org.openqa.selenium.remote.ProtocolHandshake createSession INFO: Detected dialect: OSS
My jenkins job will then end as FAILURE even though all my tests pass. I then noticed that these new output messages seem to be going to STANDARD_ERROR for some reason. When using the older java-client v4.1.2, I never had this problem.
The text was updated successfully, but these errors were encountered: