Opened 11 years ago

Last modified 8 years ago

#1134 new feature

IZ193: Need test for CR 6691982 (ARCo)

Reported by: jana Owned by:
Priority: normal Milestone:
Component: testsuite Version: current
Severity: Keywords: Sun tests
Cc:

Description

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

        Issue #:      193             Platform:     Sun           Reporter: jana (jana)
       Component:     testsuite          OS:        All
     Subcomponent:    tests           Version:      current          CC:    None defined
        Status:       NEW             Priority:     P3
      Resolution:                    Issue type:    FEATURE
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
          URL:
       * Summary:     Need test for CR 6691982 (ARCo)
   Status whiteboard:
      Attachments:

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


   Opened: Wed Apr 30 07:43:00 -0700 2008 
------------------------


The testsuite should test the AR.

Several use cases should be tested.

1. the reuse of the ar number (since this can wrap)

   ------- Additional comments from jana Wed Apr 30 07:44:37 -0700 2008 -------
The testsuite should test the AR.

Several use cases should be tested.

1. the reuse of the ar number (since this can wrap)

   ------- Additional comments from jana Wed Apr 30 08:01:58 -0700 2008 -------
The testsuite should test the AR.

Several use cases should be tested.

1. the reuse of the ar number (since this can wrap)
   A short AR should be submitted
   then the AR number reset, so the next submitted AR has the same number
   submit other AR (must have the same number)
   Arco db should be checked that there are two lines in the sge_ar tables, and
after the AR's are terminated that there are 2 entries for each AR in the
sge_ar_attribute table.

2. The reporting could be turned off and thus result in an incomplete
information in the reporting file.
   If the reporting is turned off when an AR is created and later turned on,
only ar_log line could be written in the reporting file. In that case no records
should be created in the AR tables, because the parent record in the sge_ar
could not be created.

3. The field ar_parent in sge_job_usage contains an ar_id from the sge_ar table,
uniquely identifying this, not the AR number issued by qmaster.
   Check that when AR bs are submitted, the ar_parent field contains the ar_id
of this AR from the sge_ar table. Best if the ar_id, and ar_number in sge_ar
table are not the same.

4. If reporting is turned off and only 'acct' line exist for a particular AR
job, if job-logging turned on, all job information in sge_job tables should be
created, but in the sge_job_usage table the ar_parent field should have value
-1, because the parent record does not exists in the sge_ar table.

Change History (0)

Note: See TracTickets for help on using tickets.