Ranorex Forum

We are running Ranorex 5.1 on a Windows 7, Service Pack 1, 64-bit platform.

Since some time now our tests get stuck while the console logger seems to be shutting down (At least that is the last line in the console).
The tests stay at this stage for about 7 hours until jenkins kills the process.

Is there a known issue I have not found so far or maybe even a solution for this?

Regards,
Alex

Hi Alex,

this is no know issue.
Can you give us more information about your problem please?

Regards,
Bernhard

Hi Bernhard,

first of all, I don't think, there is any use in providing information about the application, since it happened for two different AUTs now. I can only provide information about one of these though, because the issue can not be reproduced conveniently.
The log is just giving this information:
Test Run started at 2015/05/07 9:59 AM.

...
[2015/05/07 10:03:04.020][Debug ][Logger]: Console logger starting.
...
[2015/05/07 23:40:11.953][Debug ][Logger]: Console logger stopping.
Build timed out (after 1,200 minutes). Marking the build as aborted.
...

As you can see, the timeout must have been reached while the console logger was shutting down.
The next step in the Jenkins script will be an ECHO, so I am sure that the tests.exe file has not terminated until the timeout was reached.

It happened to me on my own machine once too.
The tests should stop and the message about the console logger shutting down appeared and never disappeared. I was not able to break the test run, I had to kill the test process.
It got stuck at this point for about 15 minutes on my machine until I wanted to continue working. I did not think a lot about it at this time, because there it was not happening regularly and I just thought, it might never happen again. Thus I did not save any data or the script that was executed in this case.

If there is anything that could help you, ask for it, I will try my very best to provide information.

Regards,
Alex

Hello Alex,

This is no known issue, but the version 5.1 is already outdated and is no longer supported. If there is an bug we can only fix it in the current version.
I suggest updating Ranorex to the current version and check if the issue also occurs with this version.
May I also ask if the issue also occurs without using Jenkins?

Regards,
Bernhard

We wanted to updated to the current Version anyway.
It is still ongoing though, I can't tell anything about the results so far.

But this issue also happens without Jenkins.

Regards,
Alex

Hi Alex,

Thank you for the information.
Maybe it would be better to analyze the issue on your machine directly in a remote session, but I would suggest to upgrade Ranorex first.
It would also be interesting if the issue can be reproduced in a smaller test.
Please write an email to [email protected] if it still doesn't work in the newest version.

Regards,
Bernhard

Hi Bernhard,

we found the reason for this issue and it had nothing to do with Ranorex. It just was a remaining thread that was not terminated for some reason.

Thank you anyway!
Regards,
Alex

Hi Alex,

Thank you for the information. I am glad that you could solve the problem.

Regards,
Bernhard