Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

[sophia-guo]

Pipeline shell step aborts prematurely with ERROR: script returned exit code -1, which suggests

23:40:22 TEST RESULT: Passed. Execution successful
23:40:22 --------------------------------------------------
23:41:22 wrapper script does not seem to be touching the log file in /home/jenkins/workspace/openjdk10_j9_openjdktest_ppc64le_linux@tmp/durable-6e1ee46e
23:41:22 (JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300)

https://ci.adoptopenjdk.net/view/OpenJDK%20tests/job/openjdk10_j9_openjdktest_ppc64le_linux/52/consoleFull

This issues happened intermittently. It seemed if there is no log information for a period of time pipeline will prematurely aborts and return with exit code -1. That means if some tests take longer without output may get this issue?

23:41:22 wrapper script does not seem to be touching the log file in /home/jenkins/workspace/openjdk10_j9_openjdktest_ppc64le_linux@tmp/durable-6e1ee46e

According to the message, Set master JVM with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300 may help.

[smlambert]

@sophia-guo - Do you mean a possible solution is to add the HEARTBEAT_CHECK_INTERVAL as a commandline option to the JVM that runs the Jenkins agents?

[sophia-guo]

@smlambert yes, though I don't have permission to try.

[smlambert]

I believe I do, so I can add it to the JVM_OPTIONS for the agent for all test machines. (Likely won't do this until later tonight).

[smlambert]

Added to the 2 ppcle test machines that seem to be lagging, and where we see this issue most. We can see if this will resolve the problem. If other machines also end up having this issue, we will also want to update them.

[Mesbah-Alam]

Seen this error on x86-64_linux too: https://ci.adoptopenjdk.net/view/work%20in%20progress/job/Grinder/117/console.

14:36:10 (JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300)```

[AdamBrousseau]

According to the Jenkins issue (https://issues.jenkins-ci.org/browse/JENKINS-48300?focusedCommentId=330383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-330383), you need to set the option on the JVM that runs the Jenkins master. We have added this at OpenJ9 and well as to 2 Jenkins' internal to IBM and it seems to resolve the issue.
eclipse-openj9/openj9#2356

[smlambert]

@sxa555 or @karianna , if you have permissions to Jenkins master, can you add the HEARTBEAT_CHECK_INTERVAL option as noted above? Thanks!

[karianna]

This has been added to master jenkins and it's been restarted

[karianna]

I'll let you close if the issue is resolved

[sophia-guo]

It happened again on windows. So probably we need to double check if the option is set on master or if the setting was reset by some master update?
https://ci.adoptopenjdk.net/view/Test_openjdk/job/openjdk11_j9_openjdktest_x86-64_windows/2/console

[sophia-guo]

Didn't see this issue for a long time. Assume it's solved by adding the options.

[dfoley84-zz]

Currently Facing the Above issue.. I have added the following into the Pipeline
script { System.setProperty("org.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL", "86400");

[kerthcet]

Currently Facing the Above issue.. I have added the following into the Pipeline
script { System.setProperty("org.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL", "86400");

have you solve the problem?

[ghost]

I'm getting same issue @sophia-guo please help me how to fix this issue

wrapper script does not seem to be touching the log file in $PWD@tmp/durable-48d0a171
(JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)

[smlambert]

@yudiz-vinayak - see the note in #474 (comment) about setting the -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300 (https://issues.jenkins-ci.org/browse/JENKINS-48300?focusedCommentId=330383&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-330383) - in the init script of the Jenkins server you are using.