Opened 13 years ago
Last modified 10 years ago
#1154 new enhancement
IZ213: Error checking after test execution is missing.
Reported by: | dagru | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | testsuite | Version: | current |
Severity: | Keywords: | Sun framework | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=213]
Issue #: 213 Platform: Sun Reporter: dagru (dagru) Component: testsuite OS: All Subcomponent: framework Version: current CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: milestone 1 Assigned to: issues@testsuite QA Contact: joga URL: * Summary: Error checking after test execution is missing. Status whiteboard: Attachments: Issue 213 blocks: Votes for issue 213: Vote for this issue Opened: Mon Jul 21 08:22:00 -0700 2008 ------------------------ This was reported as gridengine issue 2659: Testsuite should be enhanced so that after a test function finishes the message file of master and execution hosts is checked if it contains error messages or criticals. ------- Additional comments from aja Thu Nov 6 02:45:59 -0700 2008 ------- For checktree_arco the dbwriter log should be checked. The procedure check_dbwriter_log do this but the only test which check the content is dbwriter/bigdecimal test. Note that for some tests the error outputs are expected. If the log file would be checked for all tests globally, this should be considered.
Note: See
TracTickets for help on using
tickets.