org.openqa.selenium.remote.ProtocolHandshake createSession messages logging as errors
See original GitHub issueDescription
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
- java client build version or git revision if you use some shapshot: 5.0.0-BETA4
- Appium server version or git revision if you use some shapshot: 1.6.4-beta
- Desktop OS/version used to run Appium if necessary: Windows and OSX
- Node.js version (unless using Appium.app|exe) or Appium CLI or Appium.app|exe:
- Mobile platform/version under test: iOS and Android
- Real device or emulator/simulator: emu and sim
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.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 by maintainers)
Top GitHub Comments
@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!!!
@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.