yaobinshi / test1

test for scratch
MIT License
0 stars 0 forks source link

scheduler not recording kill msg #420

Open yaobinshi opened 9 years ago

yaobinshi commented 9 years ago

Author Name: Bob Gobeille Original Redmine Issue: 555, http://www.fossology.org/issues/555 Original Date: 2012/01/25 Original Assignee: Alex Norton


When issuing a kill command from fo_cli, the kill message should be written to jq_end_text, but it is not.

status scheduler:13825 revision:(null) daemon:2 jobs:0 log:stdout port:5555 verbose:0 job:848 status:JOB_STARTED type:ununpack, priority:0 running:1 finished:0 failed:0 kill 848 "now" Command received

At this point the ununpack job is killed, but jq_endtext contains: Failed instead of the message "now"