Unexpected end of job in jenkins using katalon to execute automatic tests

Product Forums Katalon Studio
, ,
1

Hello,

I’m executing automatic tests using katalon in console mode.

Sometimes job executed by jenkins ends unexpectedly without any error.

Logs:

  • /var/lib/jenkins/.katalon/5.10.1/Katalon_Studio_Linux_64-5.10.1/katalon -noSplash -runMode=console -projectPath=/var/lib/jenkins/workspace/ -browserType=Firefox -testSuitePath=Test Suites/MainTestingSuite
    Delete folder: Libs
    Opening project file: /var/lib/jenkins/workspace/.prj
    Request sent successfully.
    [EL Warning]: 2019-05-10 13:54:15.046–Ignoring attribute [lastRun] on class [TestSuiteEntity] as no Property was generated for it.
    Build step ‘Execute shell’ changed build result to UNSTABLE
    Got SIGTERM, exiting
    In exit
    Terminating xvnc.
    $ vncserver -kill :80
    Killing Xvnc4 process ID 29224
    Archiving artifacts
    ‘Reports/MainTestingSuite/’ doesn’t match anything, but ‘’ does. Perhaps that’s what you mean?
    No artifacts found that match the file pattern “Reports/MainTestingSuite/”. Configuration error?
    Recording test results
    ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
    Finished: FAILURE

Someone already had that problem? How to track that case? I’m waiting for your answer.

Best Regards,

2

hi,

you are using vnc server to see browser during executing?
what about mem or cpu usage %?
you are getting SIGTERM, i guess that this is caused your pc capability
this is my strong guess :slight_smile:

3

Hello,

Thank you for your answer :slight_smile:

Yes I’m using VNC for that.

I’m getting SIGTERM even when job is end successfully, and I have 4 similar jobs running tests and only that one is failing. I’ve observed memory and CPU usage and it’s not reaching maximum level at any moment.

Any idea what can I inspect next?

Regards,

4

hi,

are you able to debug where this SIGTERM occurs?
Why you have to you VNC to see browser?
Start your Jenkins as a process then you are able to see browser too-
If Jenkins is started as server then we are not able to see browser
5

Hello,

I’m not able or maybe I don’t know how to debug that SIGTERM, could you give me a hint how to do that?
And could you explain me how can I see the browser without VNC?

BTW. I’ve turned off VNC from that build and problem still occurs.

Regards,

6

And SIGTERM was from VNC ending with build, without VNC activated logs are like that:

/var/lib/jenkins/.katalon/6.0.6/Katalon_Studio_Linux_64-6.0.6/katalon -noSplash -runMode=console -projectPath=/var/lib/jenkins/workspace/<job name> -browserType=Firefox -testSuitePath=Test Suites/MainTestingSuite
Delete folder: Libs
Opening project file: /var/lib/jenkins/workspace/<job name>/<project file name>.prj
+ echo $?
1

Terminating xvnc.
$ vncserver -kill :33
Killing Xvnc4 process ID 103750
Archiving artifacts
‘Reports/MainTestingSuite/’ doesn’t match anything, but ‘’ does. Perhaps that’s what you mean?
No artifacts found that match the file pattern "Reports/MainTestingSuite/". Configuration error?
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Finished: FAILURE
7

hi,

any interesting here
/var/log/messages, /var/log/syslogd

8

Hello,

I don’t have file like ‘var/log/messages’ and in /var/log/syslog/’ where isn’t anything about jenkins jobs.

Best Regards

9

this is not related to Jenkins at all
it’s Linux kernel issue which causes my strong guess vnc service

10

The strange thing with that is:

I’ve started that job every hour with 0 minutes, so it’s started at 13:00, 14:00, 15:00 etc.

When I’ve changed it to start every hours with 5 minutes (13:05, 14:05, 15:05) problem is not occuring.

Problem also occured when that job started at 12:53, 13:53, 14:53 etc.

So maybe it is issue with server.

Thanks for your help.

11

For clarification:

I’ve finally found cause of that problem.

Katalon job failed like that, when you try executed two Katalon jobs at the moment. I’ve changed number of executors at jenkins to 1, and problem is not occuring anymore.

Best Regards