ACS-4_0_0-pre-2004-07
The ACS+ARCHIVE software has been tagged with the final tag:
ACS-4_0_0-pre-2004-07-ITER-3
These are the patches we received and integrated subsystem per subsystem:
|
SUBSYSTEM NAME |
TAG (corresponding to the last bug fixing) |
|
ACS |
ACS-4_0_0-pre-2004-07-2 |
|
ARCHIVE |
ARCHIVE-4_0_0-pre-2004-07-1 |
build: no problems
unit tests
ACS: found two problems in lkm and extpy modules.
In the lkm module the third case in the following list was not considered and it has been added to the test case.
1. Redhat 9 running RTOS kernel2. Redhat 9 with RTOS kernel built, but not running3. Redhat 9 without RTOS kernel built
In the extpy module the test Makefile failed to install the 3rd party libraries here
/alma/ACS-3.1/Python
/alma/ACS-3.1/Python/lib/python2.3
Problem was solved not installing in $PYTHON_ROOT.
ARCHIVE: found problems in running the ArchiveManager
The ArchiveManager couldn’t work with ACSDATA in a different location than the one used by the developer because there was an absolute path in the Tomcat configuration. The problem was solved updating the configuration file server.xml and changing the location of the webapps directory to $ALMASW_INSTDIR/webapps. In addition, this new directory webapps under $ALMASW_INSTDIR must be group writable. The Tomcat installation script (which is not part of the ALMA SW but comes with the ACS installation) has been accordingly modified.
General Consideration
Compared to ACS+ARCHIVE 3.1.2 the unit test percentage is slightly increased. When available, the coverage information is anyway showing poor results.
SLOC detailed figures:
Note: Starting from Release R1.1 ITS and SE have used a common approach in calculating SLOC.
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.
