NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > GrailTestPlan > GrailTestPlanResults

Changes | Index | Contents | Search | Statistics | Go

2004/12/27

Test 1: Sensitivity of Grail to restarts. Passed. System was brought up, a Cleo antenna screen was brought up, and dynamic corrections started. Grail was then stopped. An error message from AntennaCharacterization appeared. Grail was restarted. The error was cleared within 30 seconds, and dynamic corrections resumed.

Test 2: Quality of Service. Passed, on simulator. Set up with 3 accelerometer samplers running at 20 Hz each. The polling loop cycled like clockwork every 20 seconds.

Test 3: Simultaneous configurations. Partially passed. Used 3 instances of config_tool configuring simultaneously, each running 'cont1_2' configuration from http://tryllium.gb.nrao.edu/examples/configuration/c01_L. No problems. Sequential configurations with turtle. Did not undertake the turtle portion due to time spent troubleshooting Test 4, and to allow Mark time to conduct his tests.

Test 4: Turtle/Archivist issue. Failed. NOTE: This appears not to be a Grail issue. There originally was a Grail deadlock uncovered while replicating this problem on the simulator, and that was dealt with. However, further tests showed remaining issues in Turtle, while Grail remained unaffected. The issues were as follows:

1. Issue: Turtle fails when Grail returns an error due to badly formatted parameter path. The test that revealed this was:
   • Loaded project JAPI, script SetValues
   • Added line SetValues("Archivist", {"dataAssociatedParameters,19":"bogus_bogus_bogus"})
   • Submitted the script and ran it
   • When it got to this line, Grail returned an error that the parameter path dataAssociatedParameters,19 was not correct. (It is not. Grail will not handle a partial path; it requires a full path, such as dataAssociatedParameters,19,device.) This error return causes SOAPpy to throw a python exception, causing turtle.d to fail. (Is exception not handled?)
   • Further attempts to use Turtle failed
   • A careful examination of all running threads on Grail (there were 44 of them) revealed nothing out of order. Grail seemed to be running OK, was responsive both on its SOAP and M&C RPC++ interface.
2. Issue: Turtle SetValue() did not work as expected. When used, it sends the value to the manager, but does not call reg_change() or prepare(), which means one will not see the results in the Archivist until something else prepares that manager:
   • Loaded project JAPI, script SetValues
   • Added line SetValues("Archivist", {"dataAssociatedParameters,19,device":"Inclinometer", "dataAssociatedParameters,19,manager":"Inclinometer", "dataAssociatedParameters,19,sampler":"InclinometerData", "dataAssociatedParameters,19,delta":"0"})
   • Submitted the script and ran it
   • Turtle runs script OK, but no change seen on Archivist cleo window until one prepares the Archivist using the cleo window.

Test 5: Stress Tests. Currently cannot be done, because Test 2 requires the simulator. Modifications to the Grail Status server will allow results to be checked while Grail runs on the real system.

There are alternative stress tests, however. For example, Joe has a daisy pattern that takes a minute or more to load through Grail, and pegs Grail at 100% CPU usage during this period. Grail should continue responding to other requests, however. While running this on the simulator, Grail did indeed continue to service AntennaCharacterization? requests every second.

Test 6: Client Side failure tests. Passed. Ran 2 Grail clients which registered the same sampler, InclinometerData. Suspended one of them (Ctrl-Z). The other continued receiving sampler structures from Grail. Killing a client also did not affect the other client.

-- RamonCreager - 27 Dec 2004