Note : You can run the test using a shell script. It can be created with any text editor or by executing the following command: ztest@zone:~# cat > test-script.sh <<EOT
#!/bin/bash
if [ -n "\$1" ]; then
for (( i=1; i<=\$1; i++ ))
do
LOG="/var/tmp/libc-test.\$i.txt"
uname -a > \${LOG}
/opt/libc-tests/bin/libctest 2>&1 | /usr/bin/tee -a \${LOG}
percent="\$(grep 'Percent passed:' \${LOG} | sed 's/Percent passed: *//')"
folder="\$(grep 'Log directory:' \${LOG} | sed 's/Log directory: *//')"
if [ "\${percent}" == "100.0%" ]; then
sudo rm -r -f \${folder}
else
echo "Fault on \${i} pass! Just \${percent} are successfull. You can find logs in \${folder}." 2>&1 | /usr/bin/tee -a \${LOG}
exit 1
fi
done
else
LOG="/var/tmp/libc-test.\$(date +%F-%T).txt"
uname -a > \${LOG}
/opt/libc-tests/bin/libctest 2>&1 | /usr/bin/tee -a \${LOG}
fi
EOT
ztest@zone:~# sed -i '/./!d' test-script.sh && chmod 777 test-script.sh
You can run the test script in a single mode, i.e. all tests will be executed once (./test-script.sh - without parameters). After running of this script you will find the log in the /var/tmp/libc-test.<ISO TIME>.txt file. It will contain information in the format that is used in Test Results. And the second one is stability mode - for testing the libc stability. In this case you should put the number of cycles (for example, to run 1000 cycles - ./test-script.sh 1000). And now after script is finished you will find logs in the libc-test.<N>.txt form in the /var/tmp folder, where <N> - is a cycle number. |