Ask a Question

Jenkins (Failed) + TestExecute (Passed)

Occasional Contributor

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 the executions showing PASSED. 


Any suggestion if there is a setting within Jenkins that causing this issue by chance?


Hi @ApisathS 


The job build failed, but the tests themselves passed, so some other point (maybe, post-build step?) failed.

Check the Console Output of the failed build #52 which should point you to what failed. Post here or DM to me if you prefer.


Hope this helps

New Contributor

We have been experiencing the same behavior.  This started maybe two weeks ago.  Running 14.8 via a Jenkins Freestyle job.  It had been humming along for at least 6 months.

Contact customer support.  We have an open ticket but after the second response last week suggesting that we turn off the test time out in Jenkins--leading to a 3 day job run--I haven't seen a reply to my messages.

Occasional Contributor

yea, my issue started about the same time as well. 
Everything works great until 3 weeks ago. 

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. 

SmartBear Alumni (Retired)

Thanks for helping, mikef!


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

Sonya Mihaljova
Community and Education Specialist

New Contributor

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.  

Showing results for 
Search instead for 
Did you mean: