Bug #543

scheduler unable to kill a job that hasn't started

Added by Bob Gobeille over 1 year ago. Updated 7 months ago.

Status:Resolved Start date:01/25/2012
Priority:Low Due date:
Assignee:Alex Norton % Done:

0%
Category:Scheduler
Target version:-
Rank:99 Tester:

Description

In fo_cli:

kill 831 this job is no longer needed
Command received
Invalid kill command: job 0 does not exist
status
scheduler:11981 revision:(null) daemon:0 jobs:1 log:/var/log/fossology/fossology.log port:5555 verbose:1

There needs to be a way to cancel a job that hasn't started.

History

#1
Updated by Mary Laser over 1 year ago

  • Priority changed from Normal to Low

re-prioritizing

#2
Updated by Alex Norton over 1 year ago

  • Status changed from New to In Progress

#3
Updated by Bob Gobeille over 1 year ago

  • Target version changed from 2.0.0 to 2.0.1

#4
Updated by Alex Norton 12 months ago

  • Status changed from In Progress to Resolved

Fixed with svn 5913.

Users can kill jobs that have not been scheduled yet.

#5
Updated by Mary Laser 9 months ago

  • Target version deleted (2.0.1)

this should be included in 2.1.0 after it is verified.

#6
Updated by Bob Gobeille 7 months ago

  • Rank set to 99

Change unranked issues to rank 99 so they show up in a ranking report at the bottom. Otherwise, they show up on top.

Also available in: Atom PDF