[EMAIL PROTECTED] wrote on 10/04/2007 04:25:53 
PM:

> Renier Morales wrote:
> >
> > What sort of errors?
> >
> 
> Specifically I am seeing failures in the following tests:
> 
> Sensor/saHpiSensorThresholdsGet/GetThresholds
> Sensor/saHpiSensorThresholdsSet/SetUpCritical
> Sensor/saHpiSensorThresholdsSet/OutOfOrder
> HotSwap/saHpiHotSwapActionRequest/Toggle
> Power/saHpiResourcePowerStateSet/PowerCycleOn
> Power/saHpiResourcePowerStateSet/PowerCycleOff
> WatchdogTimer/saHpiWatchdogTimerReset/InvalidRequest
> WatchdogTimer/functional/Event
> WatchdogTimer/functional/PretimerEvent
> WatchdogTimer/functional/ExpirationFlags
> WatchdogTimer/saHpiWatchdogTimerSet/Running
> WatchdogTimer/saHpiWatchdogTimerGet/Countdown
> 
> 
> The full output of the test run is below.
> 
> I'm looking into these slowly but wanted to see if anything was easy to
> fix or ignore.

All of those are valid problems in the simulator plugin (I assume you are 
using that). In total there are about 13 failed test cases in the 
simulator out of 642.

        --Renier

> 
> Drew
> 
> 
> 
> 
> Sensor/saHpiSensorThresholdsGet/GetThresholds: FAIL
> 
>    [Domain:0; Resource:1; Rdr:131073; Sensor:1] LowCritical is not
> supported but it's bit is set in the RDR ReadThold field [0x76].
>    LowMajor is not supported but it's bit is set in the RDR ReadThold
> field [0x76].
>    UpMajor is not supported but it's bit is set in the RDR ReadThold
> field [0x76].
>    UpCritical is not supported but it's bit is set in the RDR ReadThold
> field [0x76].
>    PosThdHysteresis is not supported but it's bit is set in the RDR
> ReadThold field [0x76].
>        at runThresholdTest
> (src/tests/sensor/saHpiSensorThresholdsGet/GetThresholds.cc:88)
> 
> 
> Sensor/saHpiSensorThresholdsSet/SetUpCritical: ERROR
> 
>    [Domain:0; Resource:1; Rdr:131073; Sensor:1]
> saHpiSensorThresholdsSet() unexpectedly returned SA_ERR_HPI_INVALID_CMD
> instead of SA_OK.
>        at runThresholdTest
> (src/tests/sensor/saHpiSensorThresholdsSet/SetUpCritical.cc:148)
> 
> 
> Sensor/saHpiSensorThresholdsSet/OutOfOrder: FAIL
> 
>    [Domain:0; Resource:1; Rdr:131073; Sensor:1]
> saHpiSensorThresholdsSet() unexpectedly returned SA_OK instead of
> SA_ERR_HPI_INVALID_DATA.
>        at runThresholdTest
> (src/tests/sensor/saHpiSensorThresholdsSet/OutOfOrder.cc:120)
> 
> 
> HotSwap/saHpiHotSwapActionRequest/Toggle: NOTSUPPORT
> 
>    The following preconditions must be met:
> 
>       1. The resource cannot be the same resource the HPI User is 
running
>          on.
> 
>       2. The resource is in the ACTIVE or INACTIVE state.
> 
>       3. The Hot Swap Timeouts are not set to BLOCK or can be changed.
> 
> 
> 
> Power/saHpiResourcePowerStateSet/PowerCycleOn: FAIL
> 
>    [Domain:0; Resource:1] Power Cycle failed to turn entity ON.
>        at testPowerCycle
> (src/tests/power/saHpiResourcePowerStateSet/PowerCycleOn.cc:125)
>        at runPowerTest
> (src/tests/power/saHpiResourcePowerStateSet/PowerCycleOn.cc:92)
> 
> 
> Power/saHpiResourcePowerStateSet/PowerCycleOff: FAIL
> 
>    [Domain:0; Resource:1] Power Cycle didn't turn entity ON.
>        at testPowerCycle
> (src/tests/power/saHpiResourcePowerStateSet/PowerCycleOff.cc:123)
>        at runPowerTest
> (src/tests/power/saHpiResourcePowerStateSet/PowerCycleOff.cc:88)
> 
> 
> WatchdogTimer/saHpiWatchdogTimerReset/InvalidRequest: FAIL
> 
>    [Domain:0; Resource:1; Watchdog:1] saHpiWatchdogTimerReset()
> unexpectedly returned SA_OK instead of SA_ERR_HPI_INVALID_REQUEST.
>        at testWatchdogs
> (src/tests/watchdogtimer/saHpiWatchdogTimerReset/InvalidRequest.cc:183)
>        at runSessionTest
> (src/tests/watchdogtimer/saHpiWatchdogTimerReset/InvalidRequest.cc:94)
> 
> 
> WatchdogTimer/functional/Event: FAIL
> 
>    [Domain:0; Resource:1; Watchdog:1] Did not receive a Watchdog Event!
>        at verifyEvents (src/tests/watchdogtimer/functional/Event.cc:277)
>        at testWatchdogs 
(src/tests/watchdogtimer/functional/Event.cc:178)
>        at runSessionTest 
(src/tests/watchdogtimer/functional/Event.cc:95)
> 
> 
>    [Domain:0; Resource:4; Watchdog:1] Did not receive a Watchdog Event!
>        at verifyEvents (src/tests/watchdogtimer/functional/Event.cc:277)
>        at testWatchdogs 
(src/tests/watchdogtimer/functional/Event.cc:178)
>        at runSessionTest 
(src/tests/watchdogtimer/functional/Event.cc:95)
> 
> 
> WatchdogTimer/functional/PretimerEvent: FAIL
> 
>    [Domain:0; Resource:1; Watchdog:1] Did not receive a Watchdog
> PreTimeout Interrupt Event!
>        at verifyEvents
> (src/tests/watchdogtimer/functional/PretimerEvent.cc:304)
>        at testWatchdogs
> (src/tests/watchdogtimer/functional/PretimerEvent.cc:178)
>        at runSessionTest
> (src/tests/watchdogtimer/functional/PretimerEvent.cc:99)
> 
> 
>    [Domain:0; Resource:4; Watchdog:1] Did not receive a Watchdog
> PreTimeout Interrupt Event!
>        at verifyEvents
> (src/tests/watchdogtimer/functional/PretimerEvent.cc:304)
>        at testWatchdogs
> (src/tests/watchdogtimer/functional/PretimerEvent.cc:178)
>        at runSessionTest
> (src/tests/watchdogtimer/functional/PretimerEvent.cc:99)
> 
> 
> WatchdogTimer/functional/ExpirationFlags: FAIL
> 
>    [Domain:0; Resource:1; Watchdog:1] Timer Use Expiration Flags not 
reset!
>        at clearExpirationFlags
> (src/tests/watchdogtimer/functional/ExpirationFlags.cc:202)
>        at testWatchdogs
> (src/tests/watchdogtimer/functional/ExpirationFlags.cc:119)
>        at runSessionTest
> (src/tests/watchdogtimer/functional/ExpirationFlags.cc:77)
> 
> 
> WatchdogTimer/saHpiWatchdogTimerSet/Running: FAIL
> 
>    [Domain:0; Resource:1; Rdr:262145; Watchdog:1] Running was FALSE, but
> became TRUE after setting it to TRUE.
>        at checkStoppedWatchdog
> (src/tests/watchdogtimer/saHpiWatchdogTimerSet/Running.cc:181)
>        at testWatchdog
> (src/tests/watchdogtimer/saHpiWatchdogTimerSet/Running.cc:127)
>        at runWatchdogTest
> (src/tests/watchdogtimer/saHpiWatchdogTimerSet/Running.cc:99)
>        at runRdrTest (src/tests/watchdogtimer/WatchdogTestCase.cc:56)
> 
> 
> WatchdogTimer/saHpiWatchdogTimerGet/Countdown: FAIL
> 
>    Watchdog Timer should be running, but Running field is SAHPI_FALSE.
>        at testWatchdogs
> (src/tests/watchdogtimer/saHpiWatchdogTimerGet/Countdown.cc:142)
>        at runSessionTest
> (src/tests/watchdogtimer/saHpiWatchdogTimerGet/Countdown.cc:81)
> 
> 
> 
> Passed Test Cases: 0
> Blocked Test Cases: 0
> Failed Test Cases: 10
> Errored Test Cases: 1
> Not Supported Test Cases: 1
> Unknown Test Cases: 0
> Total Executed Test Cases: 12
> Total test cases: 642
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Openhpi-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to