Forum Discussion

maros's avatar
maros
New Contributor
5 years ago

[TestComplete] [WARNING] Unable to find the log file

Hi,    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] E...
  • maros's avatar
    maros
    5 years ago

    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 

maros's avatar
maros
New Contributor

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

BenoitB's avatar
BenoitB
Community Hero
5 years ago

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.

 

  • hkim5's avatar
    hkim5
    Staff
    5 years ago

    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 :)

    • sonya_m's avatar
      sonya_m
      SmartBear Alumni (Retired)
      5 years ago

      Thank you everyone for helping!

       

      maros , any updates on this? Please let us know whether you are still experiencing this.

      • maros's avatar
        maros
        New Contributor
        5 years ago

        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