Closed Deniz-Eren closed 8 months ago
Jenkins console shows the following when the failure happens:
QNX_HOST=/root/qnx710/host/linux/x86_64 QNX_TARGET=/root/qnx710/target/qnx7 MAKEFLAGS=-I/root/qnx710/target/qnx7/usr/include + docker exec --user root --workdir /root dev-env bash -c source .profile && /root/workspace/dev/.setup-profile.sh && cd /data/home/root/build_coverage && ctest --output-junit test_results.xml || (exit 0) QNX_HOST=/root/qnx710/host/linux/x86_64 QNX_TARGET=/root/qnx710/target/qnx7 MAKEFLAGS=-I/root/qnx710/target/qnx7/usr/include Test project /data/home/root/build_coverage Start 1: ssh-driver-baud-tests 1/6 Test #1: ssh-driver-baud-tests ............ Passed 6.44 sec Start 2: ssh-driver-integrity-tests
Case can be replicated when running VM target emulation with ctest from host. The driver appears to be operating correctly still when this happens, however the test-case itself hangs; most likely on a pthread_join().
Seems to happen more often if multiple instances of the QEmu emulation is running, i.e. local dev instance and Jenkins instance.
Recent robustness changes have eliminated this issue.
Jenkins console shows the following when the failure happens:
Case can be replicated when running VM target emulation with ctest from host. The driver appears to be operating correctly still when this happens, however the test-case itself hangs; most likely on a pthread_join().