Fixes:
- Much better performance is achieved by replacing the usage of
dal::get_info with custom algorithm to get information about
application tag, binary name and path
- java dvs_gui is still built and installed, but will not be
mantained any longer. Users are encouraged to use the new dvs gui. Look
into the release notes for dvs_gui package for instructions on how to
start the application.
New tests in the TDAQ tests repository:
test_host_system:
test_host_system.sh
Usage: test_host_system.sh [-v] <-fs filesize> <-ld logdir> <-ul uselimit> <-ml maxload>
Tests that the computer is ready to run TDAQ applicaitons. Checks the
filesystems usage, host load, availability of tdaq s/w directory
($TDAQ_INST_PATH) and wriatablilty of /tmp and $TDAQ_LOTH_PATH
directories. Test has partition scope. It shall be started on the
target host via PMG, and assumes that agent is there and initial ping
tests are passed. It is configured in the XML Test Repository as
Test4Class with complexity level = 2. Recommended timeout: 30 sec.
Parameters:
uselimit: limit (in percentage) on file system use. Test will
fail if at least one mounted filesystem usage exceeds the limit.
filesize: size of a temporary
file in Mb to be created in logs and /tmp directory. Test will fail if
a file can not be created (e.g. readonly mounted filesystem)
maxload: maximum allowed load
(as reported by "uptime") of the system. Test will fail if system load
exceeds this limit.
Example:
test_host_system.sh -v -fs 100 -ld $TDAQ_LOGS_PATH -ul 96 -ml 10
test_nic:
test_nic.sh
Usage: test_nic.sh [-v] <-a ip_address>
Pings the closest router from a NIC interface. Shall be run on host
where NICs is attached and described in the database. Configured in
test repository as Test4Class with complexity level = 2. Host and
parameters for templated tests are descibed as
<attr name="parameters" type="string">"-a
#this.IPAddress"</attr>
<attr name="host"
type="string">"#this.&Computer@Interfaces.UID"</attr>
Recommended timeout: 5 sec.