Opened 12 years ago

Last modified 8 years ago

#948 new defect

IZ7: performance test has to recognize unusual /tmp path

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

Description

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

        Issue #:      7               Platform:     All           Reporter: joga (joga)
       Component:     testsuite          OS:        All
     Subcomponent:    tests           Version:      current          CC:    None defined
        Status:       STARTED         Priority:     P3
      Resolution:                    Issue type:    DEFECT
                                  Target milestone: milestone 1
      Assigned to:    joga (joga)
      QA Contact:     joga
          URL:
       * Summary:     performance test has to recognize unusual /tmp path
   Status whiteboard:
      Attachments:

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


   Opened: Wed Nov 8 06:40:00 -0700 2006 
------------------------


The performance/throughput tests does a cd to /tmp and submit jobs with -cwd, to
make jobs start in /tmp - this highly reduces nfs load on the home directory
when massive amounts of jobs are started during the test.

Problem:
On some hosts (e.g. darwin architecture), a pwd in /tmp gives us /private/tmp.
When a job submitted with -cwd in /private/tmp is executed on a host of other
architecture (where there is no /private/tmp), the job will fail.

Simple solution:
test specific: Recognize such hosts, and skip the cd to /tmp on these hosts.

Advanced solution (in the testsuite framework):
Recognize such hosts during installation, create a path alias file.

   ------- Additional comments from joga Thu Dec 14 01:28:41 -0700 2006 -------
I'll take it.

   ------- Additional comments from joga Thu Dec 14 01:29:18 -0700 2006 -------
oops - set wrong state.

   ------- Additional comments from joga Thu Dec 14 01:29:42 -0700 2006 -------
I'll take it.

   ------- Additional comments from joga Thu Dec 14 01:32:07 -0700 2006 -------
Starting.

A third option might be to create a path alias file only for the specific test.
A function "create_path_alias" could take a list of paths that will be accessed
in the test, and on each exec host
- cd to the directory
- do a pwd
- create path_alias entry, if required

We probably would also need functions
- backup_path_alias
- restore_path_alias

Change History (0)

Note: See TracTickets for help on using tickets.