Opened 12 years ago
Last modified 10 years ago
#648 new defect
IZ2951: Name of -e/-o $TASK_ID differs from SGE_TASK_ID in environment
Reported by: | reuti | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.2u1 |
Severity: | Keywords: | clients | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2951]
Issue #: 2951 Platform: All Reporter: reuti (reuti) Component: gridengine OS: All Subcomponent: clients Version: 6.2u1 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: janicecritchlow (janicecritchlow) QA Contact: roland URL: * Summary: Name of -e/-o $TASK_ID differs from SGE_TASK_ID in environment Status whiteboard: Attachments: Issue 2951 blocks: Votes for issue 2951: 1 Opened: Mon Mar 9 14:45:00 -0700 2009 ------------------------ All pseudovariables for the -e/-o option have the same spelling as environment variable inside the jobscript. Exception is $TASK_ID. Maybe it could be "sychronized" with $SGE_TASK_ID in the jobscript. Also: it's value isn't replaced for jobs w/o a task specification (just a literally $TASK_ID will pop up in the name of the created file), while it is literally "undefined" in the job environment for $SGE_TASK_ID. - one doc issue - one client issue ------- Additional comments from reuti Mon Mar 9 14:47:09 -0700 2009 ------- Wrong SGE version selected. ------- Additional comments from reuti Mon Mar 9 14:48:12 -0700 2009 ------- Wrong component corrected. ------- Additional comments from reuti Wed Jun 9 15:07:42 -0700 2010 ------- Like the variable "ARC" and "SGE_ARCH" shows up twice with the same content, maybe the easiest way would be to define $TASK_ID also inside the job's supplied environment. Means the -e/-o switches are still $TASK_ID, and in the jobscript $TASK_ID and $SGE_TASK_ID can be used at your taste.
Note: See
TracTickets for help on using
tickets.