[Imported from gridengine issuezilla ​http://gridengine.sunsource.net/issues/show_bug.cgi?id=201]

        Issue #:      201             Platform:     All           Reporter: joga (joga)
       Component:     testsuite          OS:        All
     Subcomponent:    framework       Version:      current          CC:    None defined
        Status:       RESOLVED        Priority:     P3
      Resolution:     FIXED          Issue type:    DEFECT
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
          URL:
       * Summary:     cannot modify cvs release tag in testsuite config
   Status whiteboard:
      Attachments:

     Issue 201 blocks:
   Votes for issue 201:     Vote for this issue


   Opened: Thu Jul 10 03:04:00 -0700 2008 
------------------------


It is no longer possible to modify the cvs release tag in the testsuite config.
While upgrading an existing config to the current version,
the release tag was set to maintrunk.

I'd like to reset it to the actual value (e.g. V60u12_TAG),
but the config dialogue doesn't let me do it:

----------------------------------------------------------
Used cvs release tag
----------------------------------------------------------
Enter cvs release tag ("maintrunk" specifies no tag)
or press >RETURN< to use the default value.

  *  1) maintrunk

setting source_cvs_release to:
"maintrunk"

press enter...

The CVS/Tag in the source directory contains:
NV60u12_TAG

   ------- Additional comments from aja Thu Jul 10 13:46:28 -0700 2008 -------
fixed

To be able to use the name "Grid Engine", we have to pass the "standards" test in EXHIBIT B of the SISSL by running the testsuite using a (non-existent) "reference" version (see sge/LICENCES/SISSL, sge/LICENCES/standards, and sge/doc/compatibility_test.html​). Although the current version should be compatible with the last of the Sun code, it may not be compatible on the wire with any released version, e.g. because of [3532] and other possible GDI changes in 6.2u6. It would be difficult to argue against compatibility with 6.2u5, as counting, so we need to get the tests running and, if necessary, introduce a compatibility mode that hides changes like [3532] and allows us to pass the test, probably dependent on an environment variable. I don't know how sustainable that will be long-term.

If you set the urgency slots of a pe to a constant then a normal 'no flags' qstat will report that as the number of slots a job requesting the job requires: wish@iseisd-ws113:~$ qstat|tail -n +3 |awk '{print $1}'|xargs -n 1 qstat -j '{}' |grep '^{parallel';qstat parallel environment: smp range: 2 parallel environment: smp range: 2 parallel environment: smp range: 4 parallel environment: smp range: 4 parallel environment: smp range: 2-4 parallel environment: smp range: 2,3 job-ID prior name user state submit/start at queue slots ja-task-ID}

10 0.42045 fellow wish r 03/26/2013 09:13:40 all.q@… 2 13 0.41629 fellow wish r 03/26/2013 09:21:55 all.q@… 2

9 0.75000 fellow wish qw 03/26/2013 09:08:27 4

11 0.74968 fellow wish qw 03/26/2013 09:08:34 4 12 0.25536 fellow wish qw 03/26/2013 09:08:40 1 14 0.25000 fellow wish qw 03/26/2013 09:10:37 1