Bug 256758 - Global status of the parametric job is not refreshed
Summary: Global status of the parametric job is not refreshed
Status: ASSIGNED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Geclipse (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Mariusz Wojtysiak CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-27 06:45 EST by Szymon Mueller CLA
Modified: 2014-01-09 16:00 EST (History)
1 user (show)

See Also:

Attachments
Patch containing fix for this bu (10.42 KB, patch)
2008-12-02 08:18 EST, Mariusz Wojtysiak CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Mueller CLA 2008-11-27 06:45:03 EST 
To reproduce:
1. Create parametric job (for me i created parametric job which used /bin/hostname1-12 as an Executable.
2. Submit it.
3. Wait till jobs finish (for me all were ABORTED for obvious reason).
Even when all jobs were ABORTED the status of the parametric job (the "global" one) contained following statuses: [ABORTED, RUNNING, SCHEDULED, WAITING]. 
After selecting global parametric job and clicking "Update Job Status" (and waiting till all job statuses are fetched) it changed to contain only [ABORTED] status.
Comment 1 Ariel Garcia CLA 2008-11-27 12:30:26 EST 
Kasia or Mariusz, who could take care of this one?
Comment 2 Mariusz Wojtysiak CLA 2008-12-02 08:18:36 EST 
Created attachment 119265 [details]
Patch containing fix for this bu

I created a fix and tested it a bit.
But it's not safe to commit it just before release, so I'm attaching patch to apply fix after the release.
Comment 3 Mariusz Wojtysiak CLA 2008-12-02 08:21:49 EST 
This fix force refreshing status of main parametric job every time, when status of sub-job is changing.