Critical I have ran shell command in job, and when I cancelled it send SIGKILL.
Other proccess are still running:
collected 17 items [0m run-last-failure: run all (no recorded failures) ../home/tests/test_cabinet/tests/test_cabinet_apply.py::CabinetTestsApply::test_cabinet_apply [1m-------------------------------- live log call ---------------------------------[0m 2018-10-25 12:01:30 [32mINFO[0m �������������� ���� Build was aborted Aborted by Admin Recording test results ERROR: Step ?Publish JUnit test result report? failed: Test reports were found but none of them are new. Did leafNodes run? For example, /var/lib/jenkins/workspace/test_cabinet/test_result.xml is 18 min old Finished: ABORTED
[root@billing_kag (billing_tests) /]# ps aux |grep test root 1406 0.0 0.0 72144 2864 ? S 12:00 0:00 sudo -E bash /usr/lib/python2.7/site-packages/python_tools/test_utils/test_scripts/test_cabinet root 1410 0.0 0.0 106140 1920 ? S 12:00 0:00 bash /usr/lib/python2.7/site-packages/python_tools/test_utils/test_scripts/test_cabinet root 5925 0.0 0.0 6224 1436 ? S 12:01 0:00 sshpass -p zzzzzzzzzzz ssh -o StrictHostKeyChecking=no -tt -x root@localhost export PATH="/root/.pyenv/bin:$PATH"; eval "$(pyenv init -)";eval "$(pyenv virtualenv-init -)"; pyenv global 2.7.8; python2.7 /home/tests/test_cabinet/run.py root 5926 0.0 0.0 59896 6212 pts/0 Ss+ 12:01 0:00 ssh -o StrictHostKeyChecking=no -tt -x root@localhost export PATH="/root/.pyenv/bin:$PATH"; eval "$(pyenv init -)";eval "$(pyenv virtualenv-init -)"; pyenv global 2.7.8; python2.7 /home/tests/test_cabinet/run.py root 5929 0.0 0.0 106128 2932 ? Ss+ 12:01 0:00 bash -c export PATH="/root/.pyenv/bin:$PATH"; eval "$(pyenv init -)";eval "$(pyenv virtualenv-init -)"; pyenv global 2.7.8; python2.7 /home/tests/test_cabinet/run.py root 6043 0.5 0.1 236948 33016 ? S+ 12:01 0:00 python2.7 /home/tests/test_cabinet/run.py root 13825 0.0 0.0 103400 2000 ? S+ 12:02 0:00 grep test
