Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 324653

Summary:	No status or output from job submission
Product:	[Tools] PTP	Reporter:	Greg Watson <g.watson>
Component:	RM.PBS	Assignee:	Project Inbox <ptp-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	arossi, roland
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:

Description Greg Watson

2010-09-07 09:23:43 EDT

I submitted a job using PBS on abe. The job appeared in the jobs list view, then disappeared after a while. There was no output or any indication that the job run was successful or not. In other resource managers, the job status is changed to at least indicate that the job ran successfully. PBS doesn't necessarily need to do it this way, but I think there needs to be some indication of the status of the completed run.

Comment 1 Albert L. Rossi

2010-09-07 11:15:01 EDT

I did not realized that that component had specialized functionality according to RM ... I thought the same class handled this for every RM.  I will look into it.

Comment 2 Roland Schulz

2010-09-09 15:21:48 EDT

A summary what was suggested today on the call:


1) leave the jobs in the view until either a (long) timeout or the user clicks remove terminated jobs
2) report exit code ( may be change the default template to have a way to find the exit code)
3) make sure to report difference for: scheduled, running, finished

My suggestion:
We should first make sure that the above things are reported by the proxy and then make sure the UI is ok.

My question: should the proxy still have the terminated jobs in its model (thus not send the remove job event) or should the UI keep displaying the deleted ones?
if the first: then how would the UI notify the proxy about that the user clicked remove terminated jobs.

Comment 3 Greg Watson

2010-09-09 16:09:30 EDT

(In reply to comment #2)

> My question: should the proxy still have the terminated jobs in its model (thus
> not send the remove job event) or should the UI keep displaying the deleted
> ones?
> if the first: then how would the UI notify the proxy about that the user
> clicked remove terminated jobs.

There are two ways to go:

1. The proxy never sends a remove job event. The client side of the RM would need to handle the timer and removing the jobs on timeout. The UI code already handles removing the jobs when selected by the user.

2. The proxy keeps the terminated jobs in it's model and sends the remove job events after the timer expires. If the jobs have already been removed by the user, the client side would just ignore any remove jobs events for non-existent model elements.

Either option seems fine to me.

Comment 4 Greg Watson

2011-05-20 15:00:25 EDT

Superseded by new RM.