Bug #891
Selecting Pause on a scheduled job causes error in job.c
| Status: | Closed | Start date: | 02/08/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | Scheduler | |||
| Target version: | 2.1.1 | |||
| Rank: | 99 | Tester: |
Description
Using svn 5487 on randotest.ostt, I paused a job (nomos) that was scheduled but not running.... the fossology log reports:
2012-02-08 10:08:02 scheduler [13830] :: INTERFACE: new interface connection
2012-02-08 10:08:02 scheduler [13830] :: INTERFACE: received "pause 6"
2012-02-08 10:08:02 scheduler [13830] :: INTERFACE: send "received"
2012-02-08 10:08:02 scheduler [13830] :: ERROR job.c.147: job passed is NULL, cannot proceed
Also, when pause is selected, what is supposed to be displayed? The display was never changed.
To reproduce:
1. Upload from server RedHat.tar.gz and schedule nomos to run
2. Notice two unpacks and adj2nests running for this upload, cancel the two at the bottom.
3. If nomos is not running, pause it... the error should appear in the fossology.log
History
Updated by Alex Norton over 1 year ago
- Target version changed from 2.0.0 to 2.0.1
This is suffering from the same problem that http://www.fossology.org/issues/543 has and will get fixed at the same time.
Updated by Paul Holland 12 months ago
- IterNum set to 2
Updated by Alex Norton 12 months ago
Fixed with svn 5913
The scheduler now handles pausing and unpausing jobs that have not started running yet.
Updated by Alex Norton 12 months ago
- Status changed from New to Resolved
Updated by Mary Laser 9 months ago
- Target version changed from 2.0.1 to 2.1.0
Updated by Bob Gobeille 8 months ago
- Target version changed from 2.1.0 to 2.2.0
Updated by Bob Gobeille 8 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.
Updated by Mary Laser 6 months ago
- Target version changed from 2.2.0 to 2.1.1