Flooded by error messages from `gstat` when there are retrieving problems

[GoogleCodeExporter]

In case of problems with retrieving:

Too much error message, if gget could not retrieve a job.

Better a further status like "unknown" or "could not retrieve" in the 
final job list. Or an extra list with unretrieved jobs.

Original issue reported on code.google.com by timm.reu...@uzh.ch on 28 Jan 2011 at 2:16

[GoogleCodeExporter]

The GC3Utils commands *should not* be too verbose in general: this is already 
catered for.  There are good chances that the current "trunk" code (which you 
are running) prints a full error backtrace because it's supposed to be 
developer's code.

Maybe we could fix this by adding a "debug = True/False" option in the 
configuration file?

Original comment by riccardo.murri@gmail.com on 31 Jan 2011 at 2:40

[GoogleCodeExporter]

Sorry guys, my mistake:

I did not mean gget, but gstat.
(Since gget does not give a list of jobs with status.)

Sorry any inconvenience, I might have caused.

Original comment by timm.reu...@uzh.ch on 1 Feb 2011 at 10:02

[GoogleCodeExporter]

Original comment by riccardo.murri@gmail.com on 20 Jun 2012 at 3:06

• Changed title: Flooded by error messages from gget when there are retrieving problems

[GoogleCodeExporter]

Is this issue still actual ?

I would close as won't fix
and reopen a new one in case we consider to review the way backtraces 
are/should be handled

Sergio :)

Original comment by sergio.m...@gmail.com on 22 Aug 2012 at 7:33

• Changed state: Started

[GoogleCodeExporter]

Original comment by sergio.m...@gmail.com on 19 Feb 2015 at 11:20

• Changed state: WontFix

[GoogleCodeExporter]

I think the issue is still there: jobs are checked one by one, so, in case of a 
resource failure, each job will generate a distinct error message.

Original comment by riccardo.murri@gmail.com on 20 Feb 2015 at 9:12

• Changed title: Flooded by error messages from gstat when there are retrieving problems
• Changed state: Accepted