Integration Release R4.1
The software has been tagged with ALMA-R4_1
This report is base on tag Antenna-Verification-2007-03-ITER-11
To validate the software delivered for R4.1, the tests from the validation tests suite at the ITS twiki page have been run.
In addition, the report at the twiki page R4_1 has been prepared.
A) Short summary:
|
Number |
Test |
Type |
Result |
|
1 |
MDB 0th order test |
simple test on sending monitor points to the archive |
FAIL |
|
2 |
APDM test |
check on the consistency of the APDM |
PASS |
|
3 |
Control-DataCapturer test |
mini-integration test |
PASS |
|
4 |
Optical Pointing e2e test |
e2e test processing an OP SB |
FAIL |
|
5 |
Shared Simulator e2e test |
e2e test processing an SS SB |
FAIL |
|
6 |
Holography e2e test |
e2e test processing an HG SB |
PASS |
|
7 |
ACACORR integration test |
tests suite on the ACACORR software |
FAIL |
Percentage of success on the total number of tests: 42,86%
Important remark: the e2e tests 4 to 6 do not have yet the validation of the ASDM produced during the test. At the moment, the validation has to be done manually by people who know enough about the ASDM, after the test has been run. If the e2e test passes, but the validation of the ASDM fails or is missing, the e2e test is marked as FAIL.
Short overview on the test cases run in the STEs:
| Total number of test cases available | 57 |
|---|---|
| Total number of test cases executed | 57 |
| PASSED | 46 |
| FAILED | 11 |
| Total number of test cases not executed | 0 |
Short overview on the Jira tickets dealt with in the STE (simulation):
| Total number of Jira tickets about R4.1 | 20 |
|---|---|
| Newly opened Jira tickets for R4.1 | 20 |
| Old jira tickets still to be solved for R4.1 | 0 |
B) Detailed summary with problems encountered:
1) MDB 0th order test
At the beginning we experienced the following error:
2007-04-27T09:50:38.713 [GlobalLogger] Logging proxy successfully created.2007-04-27T09:50:38.715 Local file logger: Cache saved to './tmp/acs_local_log_cleanMonitorDataTest_22732'.2007-04-27T09:50:38.767 [GlobalLogger] ManagerReference generated using localhost address: 'corbaloc::10.192.1.10:3000/Manager'2007-04-27T09:50:38.955 [GlobalLogger] connecting to db with user =MONITORTEST, location=//almadev1.hq.eso.org:1521/aarchive1Exception caught while connect to //almadev1.hq.eso.org:1521/aarchive1 using user:MONITORTESTError number: 12514ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Than we changed in the file dbConfig.properties the line
from
archive.monitorDB.service=aarchive1
to
archive.monitorDB.service=alma1
and the problem disappeared. (to be checked in almadev1)
After that the test still failed due to missing tables. To be checked by archive people.
2007-04-30T13:16:16.105 [GlobalLogger] Logging proxy successfully created.
2007-04-30T13:16:16.105 Local file logger: Cache saved to './tmp/acs_local_log_cleanMonitorDataTest_21732'.
2007-04-30T13:16:16.133 [GlobalLogger] ManagerReference generated using localhost address: 'corbaloc::10.192.1.5:3000/Manager'
2007-04-30T13:16:16.181 [GlobalLogger] connecting to db with user =MONITORTEST, location=//almadev1.hq.eso.org:1521/alma1
cleaning FLOATPROPERTY
Table Not found : FLOATPROPERTY
cleaning STRINGPROPERTY
Table Not found : STRINGPROPERTY
cleaning BOOLEANPROPERTY
Table Not found : BOOLEANPROPERTY
cleaning DOUBLEPROPERTY
Table Not found : DOUBLEPROPERTY
cleaning INTEGERPROPERTY
Table Not found : INTEGERPROPERTY
done
2) Optical Pointing e2e test
This test has been done using a project file provided by Troncoso via email on April the 10th. The final version is till not in CVS since it was created at ATF and was still not considered a valid one. The test is not always working. It passes about 1 out 3 attempts. When it fails the following error is issued:
007-04-12T10:13:32.242 INFO
[CONTROL/Array001/DATACAPTURER] DataCapturer CONTROL/Array001/DATACAPTURER:
startSubscan - subscan number 1
2007-04-12T10:13:32.243 INFO [CONTROL/Array001/DATACAPTURER] hha:4594 02182
1
Exception in thread "Thread-32" org.omg.CORBA.UNKNOWN:
Server-side Exception: null vmcid: 0x41540000 minor code: 98
completed: Maybe
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:173)
at
org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:326)
at
org.jacorb.orb.Delegate.invoke_internal(Delegate.java:967)
at org.jacorb.orb.Delegate.invoke(Delegate.java:868)
at
org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at
alma.Control._ScriptExecutor2Stub.runSource(_ScriptExecutor2Stub.java:31)
at
alma.Control.Array.AutomaticArrayOperationalState$SBExecutor.run(AutomaticArrayOperationalState.java:285)
at
java.lang.Thread.run(Thread.java:595)
ping received, container alive. Memory usage 6238 of 6784 kB (= 9.6% of JVM
growth limit 64832 kB)
CONTROL/ACC/PYTHON
2007-04-12T10:13:32.000 None Main - Scan #16 is '4594 02182 1' at an (RA,
Dec) of (311.88940438, 80.55226046) degrees
2007-04-12T10:13:32.000 None Main - Its approximate (Az, El) is
(10.8487124075, 37.48709565) degrees
omniORB: Caught an unexpected Python exception during up-call.
3) Holography e2e test
The final project is still not in CVS and the test is based on the aot file provide by Dressel on April the 13th and manually modified:
in the CCL script as follows: In the HG script, after the lines:# Set up the hardwarethMC.initializeHardware() Add the following lines:thDSP = thMC.getHolographyDSP()thDSP.hwSimulation()thR = thMC.getHolographyReceiver()thR.hwSimulation()
4) Shared Simulator e2e test
The test is not passing and is reporting the same error as point 1.
5) ACACORR integration test
1 - 2007-04-30T10:36:14.759 [GlobalLogger - ] Logging proxy successfully created.
1 - 2007-04-30T10:36:14.760 Local file logger: Cache saved to '/alma/src/Antenna-Verification-2007-03-ITER-11/ACACORR/Integ/SharedSim_ACACCC/test/tatlogs/run4554/acs_local
_log_testCompleteCommunication_4674'.
1 - 2007-04-30T10:36:14.796 [GlobalLogger - maci::MACIHelper::resolveManager]
1 - 2007-04-30T10:36:14.799 [GlobalLogger - maci::MACIHelper::resolveManager] ManagerReference generated using localhost address: 'corbaloc::10.192.1.15:3000/Manager'
1 - 2007-04-30T10:36:14.800 [GlobalLogger - maci::MACIHelper::resolveManager]
1 - 2007-04-30T10:36:14.801 [GlobalLogger - maci::MACIHelper::resolveManager] Resolving reference: 'corbaloc::10.192.1.15:3000/Manager'
1 - 2007-04-30T10:36:14.811 [GlobalLogger - maci::MACIHelper::resolveManager] Manager reference narrowed.
1 - 2007-04-30T10:36:14.835 [GlobalLogger - ] Logged in.
1 - 2007-04-30T10:36:14.838 [GlobalLogger - ] Getting component: 'curl:///ACACORR/MAINTENANCE'. Creating it...
1 - 2007-04-30T10:36:18.733 [GlobalLogger - ] Get component is failed: FILE[testCompleteCommunication.cpp] LINE[128]
1 - 2007-04-30T10:36:18.734 [GlobalLogger - ] Destroying CORBA...
1 - 2007-04-30T10:36:18.737 [GlobalLogger - ] Client destroyed.
- on all the directories Data for ACS R4.0 are not correct due to a calculation done on not excluded tools
SLOC detailed figures:
Note: Starting from Release R1.1 ITS and SE have used a common approach in calculating SLOC.
Assessment on the sufficiency of Doxygen-like in-line documentation: Missing due to NRI crash
|
Modules inline |
Global inline
|
|
ITS Missing due to NRI crash |
ITS Missing due to NRI crash |
See the log at this link.
You will have a page with the results per each subsystem (see list below). In this page of results, there is a table with 3 columns:
- the first one lists the modules belonging to the subsystem,
- the second gives the results of the tests (PASSED, FAILED, UNDETERMINED, when it is neither PASSED nor FAILED); sometimes the test directory can be missing, so you will just see the message: "No test directory, nothing to do here".
- the third one gives a resume produced by Purify/Coverage reporting the analysis results on:
Functions
Functions and exits
Statement blocks
Implicit blocks
Decisions
Loops
The values reported for every item in the list above give the number of hits for that item.
In the same cell with the resume there is a link to the "Complete Report" produced by Purify. In the Complete Report one has information about the lines where the hit happened. For a loop, one has also the values: 0 (the loop is executed without entering into it), 1 (the loop is entered once), 2+ (the loop is entered and repeated once or more times).
Sometimes, instead of the resume, you will see a message like:
ERROR: No coverage info available
No atlout.spt
This happens when the modular test of that module is a fake one (for example the test is actually just an "echo something"), so there is no code (Java, Python or Cpp) that can be instrumented.
Note: the Test Coverage Analysis is not yet stable. Work is in progress to improve the results. You will see errors like:
This means that the test exists and is executed but Purify is not able to dump the information collected in the result file. This error is under investigation. We had 5 cases in ACS only
still under investigation, we don't know yet the reasons
We hope to clarify the problems under investigation as soon as possible!
See the list at this link. Missing due to NRI crash
See details at this link.
