Nick Dimiduk created YETUS-930:
----------------------------------
Summary: Interrupt signal not pushed down to running tool
Key: YETUS-930
URL: https://issues.apache.org/jira/browse/YETUS-930
Project: Yetus
Issue Type: Improvement
Components: Precommit
Reporter: Nick Dimiduk
Interrupting a running build from a Jenkins job takes a little while. Looks
like the interrupt request isn't pushed down to, in this case, the running
maven process. From the Jenkins log
{noformat}
19:15:34 cd
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1020/src
19:15:34 /usr/share/maven/bin/mvn --batch-mode
-Dmaven.repo.local=/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1020/yetus-m2/hbase-master-patch-1
clean verify -fae --batch-mode -pl hbase-shaded/hbase-shaded-check-invariants
-am -Dtest=NoUnitTests -DHBasePatchProcess -Prelease -Dmaven.javadoc.skip=true
-Dcheckstyle.skip=true -Dfindbugs.skip=true >
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1020/out/branch-shadedjars.txt
2>&1
Aborted by ndimiduk
19:17:42 Sending interrupt signal to process
Click here to forcibly terminate running steps
Aborted by ndimiduk
19:18:02 After 20s process did not stop
19:18:12 Sending interrupt signal to process
Click here to forcibly terminate running steps
{noformat}
The Yetus process does honor the interrupt request, so I don't think it's a
bug. Simply could be better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
