Opened 4 years ago

Closed 4 years ago

#1546 closed defect (fixed)

qsub -terse option performs oddly with non critical errors

Reported by: agrothberg Owned by:
Priority: normal Milestone:
Component: sge Version: 8.1.8
Severity: minor Keywords:
Cc:

Description

I am trying to submit a job using the -terse option:

$ qsub -terse  -S /usr/bin/python hello_world_delay.py 1> /dev/null
Unable to run job: warning: ec2-user's job is not allowed to run in any queue
Your job 33 ("hello_world_delay.py") has been submitted
Exiting.

The job IS actually submitted but terse does not work correctly.

The entire message is alo sent to standard err (this produces no output):

$ qsub -terse  -S /usr/bin/python hello_world_delay.py 2> /dev/null

Change History (3)

comment:1 Changed 4 years ago by dlove

  • Resolution set to fixed

$ qsub -terse -S /usr/bin/python hello_world_delay.py 1> /dev/null
Unable to run job: warning: ec2-user's job is not allowed to run in any
queue

I assume -w w is picked up from a request file.

The job IS actually submitted but terse does not work correctly.

It's a warning that it can't currently run. I'm not sure the logic is
right, but I've never got round to looking at it.

The entire message is alo sent to standard err (this produces no output):

See change [4808]: Print error messages to stderr and don't print on
success with -terse

comment:2 Changed 4 years ago by agrothberg

I am using 8.1.8 and it does not seem to be working correctly with terse in
this case. The submission was successful but nothing is printed to stdout.

On Sun, Jul 19, 2015, 06:41 SGE <sge-bugs@…> wrote:

#1546: qsub -terse option performs oddly with non critical errors


Reporter: agrothberg | Owner:

Type: defect | Status: new

Priority: normal | Milestone:

Component: sge | Version: 8.1.8

Severity: minor | Resolution: fixed
Keywords: |


Changes (by dlove):

  • resolution: => fixed

Comment:

$ qsub -terse -S /usr/bin/python hello_world_delay.py 1> /dev/null
Unable to run job: warning: ec2-user's job is not allowed to run in any
queue

I assume -w w is picked up from a request file.

The job IS actually submitted but terse does not work correctly.

It's a warning that it can't currently run. I'm not sure the logic is
right, but I've never got round to looking at it.

The entire message is alo sent to standard err (this produces no

output):

See change [4808]: Print error messages to stderr and don't print on
success with -terse

--
Ticket URL: <https://arc.liv.ac.uk/trac/SGE/ticket/1546#comment:1>
SGE <https://arc.liv.ac.uk/trac/SGE>
Son of Grid Engine: Community continuation of work on Grid Engine

comment:3 Changed 4 years ago by dlove

  • Status changed from new to closed

I am using 8.1.8 and it does not seem to be working correctly with terse
in
this case. The submission was successful but nothing is printed to stdout.

The fix was made after 8.1.8.

Note: See TracTickets for help on using tickets.