[TestComplete] [WARNING] Unable to find the log file
Lately i am getting an error from jenkins:
[TestComplete] Test runner exit code: 3. [TestComplete] [WARNING] Unable to find the log file "1584677036004.htmlx". [TestComplete] [WARNING] Errors occurred during the test execution.
My tests run with TestExecute on jenkins every night for almost a year, but this error appeared out of nowhere and I can't find the cause of it. The main problem is that without any changes made, sometimes the error appears and sometimes not. But most times it does. And therefore I can't get any report from the build, which makes my nightly build irrelevant. When I run the tests localy on my desktop, the report appears everytime.
Thank you very much
Solved! Go to Solution.
Thank you, but I don't think that might be the issue, because without proper network, all my tests would fail. But it will try to dig into network as well, thank you
Lot of small and temporary unavailability can occurs (most of them because of the incredible stack of software existing nowadays in the system). You tell that on local it always work .. so it's seem to be a network ressource problem (naming, pipe, access, .....).
Check as always the Windows event log to perhaps find a clue and monitor the network.
Un sourire et ça repart
is the job just triggered periodically?
Where are the files stored on that remote location utilizing TestExecute?
Perhaps if you are open to some changes to that build, pulling the tests from a code repository inot your jenkins slave workspace for your nightly builds it may be more robust against the "file not found" error.
just throwing up some ideas here 🙂
Thank you everyone for helping!
@maros , any updates on this? Please let us know whether you are still experiencing this.
Community and Education Specialist
hello, yes i am still having this issue. The workaround seems to be to skip some scenarios in Test suite file. I found two scenarios which are causing the problem, but I have no idea why. They are the same BDD scenarios like hundred others, but since I added them to test suite, reports are malfunctioning. So no solution now, just workaround
Thanks for the update, @maros.
Let me mark your workaround as a temporary solution. Please let us know when you find a proper solution or continue the discussion to identify the one.
SmartBear Community and Education Manager