Project

General

Profile

Bug #6824

Inconsistent argument specification

Added by Neha Sharma over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
08/19/2014
Due date:
% Done:

100%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

Hi

When using jobsub client commands, <argument><value> specification should be consistent ('=' should be required for all or none)

-N=10 fails
-N 10 works
--OS=SL5,SL6 works

-bash-4.1$ /usr/local/jobsub/client/jobsub_submit --resource-provides=usage_model=FERMICLOUD -N 10 --OS=SL5,SL6 --group nova file:///cloud/login/neha/testjob-gwms1.sh
Server response code: 200
Response OUTPUT:
/fife/local/scratch/uploads/nova/neha/2014-08-19_103032.381070_4633

/fife/local/scratch/uploads/nova/neha/2014-08-19_103032.381070_4633/testjob-gwms1.sh_20140819_103032_27006_0_1.cmd

submitting....

Submitting job(s)..........

10 job(s) submitted to cluster 75590.

JobsubJobId of first job:

Use job id to retrieve output

Remote Submission Processing Time: 0.675477981567 sec
-bash-4.1$

- Neha

History

#1 Updated by Parag Mhashilkar about 6 years ago

  • Assignee set to Dennis Box
  • Target version set to v1.0.2

#2 Updated by Dennis Box about 6 years ago

There is a consistent behavior here, it is a GNU/POSIX convention.

Single dash options can only be one letter and there is an option to the argument there is no '=' and the space is optional.

Example

-N 10 valid
-N10 valid
-N=10 invalid

Double dash options must be more than one letter, and if the option takes an argument a space or an '=' is required

Examples
--num_jobs 10 valid
--num_jobs=10 valid
--num_jobs10 invalid

#3 Updated by Dennis Box about 6 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#4 Updated by Parag Mhashilkar about 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF