Hello Colin, Yes this sockfd test has passed on Artful i386 ADT test.
But for Zesty i386, it failed with a different error: 22:46:46 DEBUG| [stdout] sockfd STARTING 22:46:51 DEBUG| [stdout] sockfd RETURNED 137 22:46:51 ERROR| [stderr] /tmp/autopkgtest.IXyugT/build.zB5/linux-4.10.0/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh: line 96: 10762 Killed ./stress-ng -v -t ${DURATION} --${s} ${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE} 22:46:51 DEBUG| [stdout] sockfd BADRET (unknown return status 137)
Hello Colin,
Yes this sockfd test has passed on Artful i386 ADT test.
But for Zesty i386, it failed with a different error: t.IXyugT/ build.zB5/ linux-4. 10.0/autotest/ client/ tests/ubuntu_ stress_ smoke_test/ ubuntu_ stress_ smoke_test. sh: line 96: 10762 Killed ./stress-ng -v -t ${DURATION} --${s} ${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
22:46:46 DEBUG| [stdout] sockfd STARTING
22:46:51 DEBUG| [stdout] sockfd RETURNED 137
22:46:51 ERROR| [stderr] /tmp/autopkgtes
22:46:51 DEBUG| [stdout] sockfd BADRET (unknown return status 137)