
To reduce the time on sanity testing, we remove variable SHARE_IMAGE and use a new variable TEST_SERIALIZE in local.conf. It is by default set to 1. Poky will copy and boot the to-be tested image for only once. It will not remove or kill the image and test cases will be serialized executed against the same image. If it is set to 0, image is always be copied for each cases, which takes much time. I had a experiment that latest qemuppc sato only takes 7 minutes to finish 9 sanity test cases, which takes more than 20 minutes before. I also removed sanity case "boot" from sato/sdk/lsb because the other cases for these targets already cover the check point of "boot". Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
1.2 KiB
Executable File
#!/bin/bash
Compiler Test Case for Sanity Test
The case boot up the Qemu target with poky-qemu qemuxxx
.
Then check if gcc/g++/make command can work in target.
Author: Jiajun Xu jiajun.xu@intel.com
This file is licensed under the GNU General Public License,
Version 2.
. $POKYBASE/scripts/qemuimage-testlib
TIMEOUT=400 RET=1
Start qemu and check its network
Test_Create_Qemu ${TIMEOUT}
If qemu network is up, check ssh service in qemu
if [ $? -eq 0 ]; then Test_Info "Begin to Test SSH Service in Qemu" Test_SSH_UP ${TARGET_IPADDR} ${TIMEOUT} RET=$? else RET=1 fi
Check if gcc/g++/make can work in target
if [ $RET -eq 0 -a -f $TOOLS/compiler_test.sh ]; then # Copy compiler_test.sh into target Test_Target_Pre ${TARGET_IPADDR} $TOOLS/compiler_test.sh if [ $? -eq 0 ]; then # Run compiler_test.sh to check if gcc/g++/make can work in target Test_SSH ${TARGET_IPADDR} "sh $TARGET_TEST_DIR/compiler_test.sh" RET=$? else RET=1 fi fi
if [ ${RET} -eq 0 ]; then Test_Info "Compiler Test PASS" Test_Kill_Qemu Test_Print_Result "compiler" 0 exit 0 else Test_Info "Compiler FAIL, Pls. check above error log" Test_Kill_Qemu Test_Print_Result "compiler" 1 exit 1 fi