Forum Discussion

ApisathS's avatar
ApisathS
Occasional Contributor
3 years ago

Jenkins (Failed) + TestExecute (Passed)

Hi Everyone,  Not sure if anyone ran into this issue before. We have Jenkins set up to run our test script. When Jenkins finished, Jenkins showed as FAILED run but when checking the result. All ...
Test Results
web testing
ApisathS's avatar
ApisathS
Occasional Contributor

I will try this out too. With my current setting, it was working without any issue until these past few weeks. 
Will add some post-build. Hopefully, this will help. 

sonya_m's avatar
sonya_m
SmartBear Alumni (Retired)
3 years ago

Thanks for helping, mikef!

 

Hi qa_qed and ApisathS, any luck solving this using the suggested approach?

  • qa_qed's avatar
    qa_qed
    New Contributor
    3 years ago

    We have no resolution so far.  If the timeout setting in the TestComplete Jenkins plug in is enabled, then the exit error code (in the console log of Jenkins) is -8.  When the timeout is disabled, the exit error code is -1 (this was suggested by support and may help resolve other similar issues).  The latter code relates to licenses, but the license is valid as all tests are completed successfully.  Also, it may only be occurring on a single test project in the whole suite because that specific project returns the error when run in isolation.  Oddly, there were no changes to it around the time the problem started presenting.