Custom Query (431 matches)
Results (46 - 48 of 431)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1142 | wontfix | IZ201: cannot modify cvs release tag in testsuite config | joga | |
Description |
[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 |
|||
#1296 | wontfix | ensure compatibility with 6.2u5 to pass "standards" test | admin | |
Description |
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. |
|||
#1457 | wontfix | qstat reports urgency slots rather than real/range value | wish | |
Description |
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
|