1. Setup VM with:
CPU - 4
Memory - 8GB
Hard disk - 100GB
Have to use DEBUG build, where we have debug macro
Setup process is described in this instruction.
Note : If you already created dilos_BASE BE according the instruction, and there is no any new tested stable version, just execute the following command:
beadm activate dilos_BASE
In other case if you have already the dilos_ISO_orig BE - make the command:
beadm activate dilos_ISO_orig
Then reboot and start the instruction from the section Step 6. Prepare VM for Tests Running:
reboot
If you have no one of these 2 BEs then start the instruction from the beginning.
Note : Create ztest user if you forgot to do it according the instruction:
sudo useradd -m -d /var/ztest -g staff -s /bin/bash ztest
sudo passwd ztest
echo "ztest ALL=(ALL:ALL) NOPASSWD: ALL" >> /etc/sudoers.d/ztest
2. Install packages for LIBC tests:
Note : If you already did it on the previous step when preparing VM to run, then you can skip this step and go to the next one.
sudo apt update sudo apt install system-test-libctest testrunner python3 build-essential
3. Login by user ztest and run tests:
sudo /opt/libc-tests/bin/libctest
Wait for about 5 minutes and found full logs at:
/var/tmp/test_results/<ISO TIME>
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
CLOG="/var/tmp/libc-stability.\$(date +%F-%T).txt"
echo "=== Stability libc tests \$(date +%F-%T) ===" > \${CLOG}
for (( i=1; i<=\$1; i++ ))
do
echo "------------------ Pass \${i} ---------------------" 2>&1 | /usr/bin/tee -a \${CLOG}
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:[ \\t]*//; s/[ \\t]*\$//')"
folder="\$(grep 'Log directory:' \${LOG} | sed 's/Log directory:[ \\t]*//; s/[ \\t]*\$//')"
rt="\$(grep 'Running Time:' \${LOG} | sed 's/Running Time:[ \\t]*//; s/[ \\t]*\$//')"
echo " Percent passed: \${percent}" >> \${CLOG}
echo " Running Time: \${rt}" >> \${CLOG}
if [ "\${percent}" == "100.0%" ]; then
sudo rm -r -f \${folder}
else
echo " PASS \${i} IS FAILED! (See \${LOG})" >> \${CLOG}
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 the common log will be placed to the /var/tmp/libc-stability.<ISO TIME>.txt file, and you will find logs about separate cycles in libc-test.<N>.txt form in the /var/tmp folder, where <N> - is a cycle number.