Opened 12 years ago

Last modified 9 years ago

#1078 new defect

IZ137: Strange errors when the $USER env.variable is not set

Reported by: petrjung Owned by:
Priority: normal Milestone:
Component: testsuite Version: current
Severity: Keywords: framework
Cc:

Description

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

        Issue #:      137             Platform:     All           Reporter: petrjung (petrjung)
       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:     mpospisil
          URL:
       * Summary:     Strange errors when the $USER env.variable is not set
   Status whiteboard:
      Attachments:

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


   Opened: Fri Jul 27 07:01:00 -0700 2007 
------------------------


Can you add to the validation in start of testsuite, if no $USER env.variable is
defined, the whoami is used or some warning is shown?

This environment variable is not used, if a valid configuration exists, but in
case of creating a new configuration from scratch, the check commands are done
as a $USER user. If no such user is set,then every try to login as user "" will
produce a couple of stretch messages in testsuite.

   ------- Additional comments from mpospisil Wed Aug 1 00:44:41 -0700 2007 -------
In the config.tcl file within the config_testsuite_root_dir function, there is a
condition to see if checking for the $USER environment variable fails, but there
is not condition to see if this variable is empty.

   ------- Additional comments from mpospisil Thu Aug 16 07:26:39 -0700 2007 -------
Added check to see if $USER environment variable is empty before installation
continues.

Change History (0)

Note: See TracTickets for help on using tickets.