Opened 10 years ago

Last modified 9 years ago

#1254 new defect

IZ313: issue_1161 test fails

Reported by: pollinger 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=313]

        Issue #:      313             Platform:     All           Reporter: pollinger (pollinger)
       Component:     testsuite          OS:        All
     Subcomponent:    tests           Version:      current          CC:    None defined
        Status:       RESOLVED        Priority:     P3
      Resolution:     FIXED          Issue type:    DEFECT
                                  Target milestone: milestone 1
      Assigned to:    pollinger (pollinger)
      QA Contact:     joga
          URL:
       * Summary:     issue_1161 test fails
   Status whiteboard:
      Attachments:

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


   Opened: Fri Nov 20 01:53:00 -0700 2009 
------------------------


The issue_1161 test fails with this logging:


/scratch3/hp150085/ts_current/bin/sol-amd64/qconf -mc} {{A
complex1161} {unknown complex attribute type 0}

----------------------------------------------------------------
"/tmp/pid-29956-1eaGG6" 55L, 4501C written
Complex attribute configuration has not been changed

_exit_status_"expect out buffer is:
   ""
this doesn't match any given expression:
   "unknown complex attribute type 0"
   "___ABCDEFG___"
   "___ABCDEFG___"
   "___ABCDEFG___"
   "___ABCDEFG___"
   "___ABCDEFG___"
----------------------------------------------------------------

These are two bugs:
1. "Complex attribute configuration has not bee changed" - if the configuration
is not changed, the test doesn't do what it should.

The reason is:
In the first line it starts the "qconf -mc" and adds "complex1161" in a new
line. But the new complex is added in the second line (due to the vi command
"A"), which is between the first two comment lines. If it is configured so, a
vim automatically adds a comment character "#" at the beginning of the new line,
because there was one in the line above.
Instead, a "5jA\ncomplex1161" should always work.

2. The test fails while the binary works without errors

The reason is:
The error message of qconf change. Instead of MSG_SGETEXT_UNKNOWN_ATTR_TYPE_U
qconf returns MSG_CENTRY_NULL_SHORTCUT_S.

   ------- Additional comments from pollinger Fri Nov 20 01:54:37 -0700 2009 -------
Taking over

   ------- Additional comments from pollinger Fri Nov 20 01:55:09 -0700 2009 -------
Fixing this issue

   ------- Additional comments from pollinger Fri Nov 20 02:27:49 -0700 2009 -------
The second bug doesn't occur when the complex is added to the right place.

Fixed this bug.

Change History (0)

Note: See TracTickets for help on using tickets.