Opened 11 years ago

Last modified 9 years ago

#1214 new defect

IZ273: jgdi shell test is broken

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

Description

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

        Issue #:      273             Platform:     All           Reporter: pollinger (pollinger)
       Component:     testsuite          OS:        All
     Subcomponent:    tests           Version:      current          CC:    None defined
        Status:       NEW             Priority:     P1
      Resolution:                    Issue type:    DEFECT
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
          URL:
       * Summary:     jgdi shell test is broken
   Status whiteboard:
      Attachments:

     Issue 273 blocks:   306 306
   Votes for issue 273:         Vote for this issue


   Opened: Fri Dec 12 10:57:00 -0700 2008 
------------------------


jgdi test is broken, gives unpredictable results.

   ------- Additional comments from pollinger Fri Dec 12 10:59:20 -0700 2008 -------
See description of "Running Testsuite in SGE QA Phases", "JGDI Tests" to
reproduce this error.

   ------- Additional comments from crei Tue Feb 17 06:34:39 -0700 2009 -------
Increment Priority: Reason this test seems not to work at all

Problem: Test reports success, but the mail content shows different "outcome"!

Test reports lots of error emails like:
"SGE 6.2u2 (default) - testsuite - JGDI_shell_test_queue_1 -- error" containing
...
qconf -Aq" client vs java:   ERROR
etc, etc,
...

At least it reports the following:
SGE 6.2u2 (default) - testsuite - JGDI SHELL STATISTICS for QCONF -- success

testsuite - JGDI SHELL STATISTICS for QCONF
------------------------------------------

 started: Tue Feb 17 13:54:19 MET 2009
finished: Tue Feb 17 13:54:19 MET 2009
  result: success
------------------------------------------

QCONF OPTIONS
=============
Tests passed:  0/12 ( 0.00% )
Total qconf options: 131
Test coverage: 12/131 ( 9.16% )
   PASSED:     0/131 ( 0.00% )
   FAILED:     12/131 ( 9.16% )
   NOT_TESTED: 62/131 ( 47.33% )
   MISSING:    57/131 ( 43.51% )

OPTION LISTS:
   PASSED:
   FAILED:     -Ahgrp -Aq -Mhgrp -Mq -dhgrp -dq -shgrp -shgrp_resolved
-shgrp_tree -shgrpl -sq -sql
   NOT_TESTED: -Acal -Ackpt -Ae -Ap -Aprj -Arqs -Astree -Auser -Mcal -Mckpt -Me
-Mp -Mprj -Mrqs -Mstree -Muser -acal -ackpt -aconf -ae -ahgrp -ap -aprj -aq
-arqs -astree -au -auser -dcal -dckpt -de -dp -dprj -drqs -dstree -duser -ke
-kec -kej -km -mcal -mckpt -mconf -me -mhgrp -mp -mprj -mq -mrqs -msconf -mstree
-mu -muser -scal -sckpt -se -sel -sp -sprj -srqs -sstree -suser
   MISSING:    -aattr -Aattr -Aconf -ah -am -ao -as -astnode -Au -clearusage -cq
-dattr -Dattr -dconf -dh -dm -do -ds -dstnode -du -dul -help -ks -mattr -Mattr
-mc -Mc -Msconf -mstnode -Mu -purge -rattr -Rattr -sc -scall -sckptl -sconf
-sconfl -secl -sep -sh -sds -srqsl -sm -so -sobjl -spl -sprjl -ss -sss -ssconf
-sstnode -rsstnode -su -sul -suserl -tsm



I would not state the result as "success":

Tests passed:  0/12 ( 0.00% )
Total qconf options: 131
Test coverage: 12/131 ( 9.16% )
   PASSED:     0/131 ( 0.00% )
   FAILED:     12/131 ( 9.16% )
   NOT_TESTED: 62/131 ( 47.33% )
   MISSING:    57/131 ( 43.51% )


   ------- Additional comments from crei Fri Apr 17 00:58:48 -0700 2009 -------
test never report errors, but output shows errors

Test coverage: 12/131 ( 9.16% )
   PASSED:     0/131 ( 0.00% )

This means 0 from 131 tests passed !!!

Test is part of qa - raising priority

Change History (1)

comment:1 Changed 9 years ago by dlove

  • Priority changed from highest to normal
  • Severity set to minor
Note: See TracTickets for help on using tickets.