https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2284/steps/12/logs/stdio qemux86-64-ptest tumbleweed-ty-3 {'tcl': ['socket.test']}
==== socket-14.12 [socket -async] background progress triggered by [fconfigure -error] FAILED ==== Contents of test case: set s [socket -async localhost [randport]] for {set i 0} {$i < 50} {incr i} { set x [fconfigure $s -error] if {$x != ""} break after 200 } set x ---- Result was: ---- Result should have been (exact matching): connection refused ==== socket-14.12 FAILED
Filed upstream in an attempt to get some interest: https://core.tcl-lang.org/tcl/tktview?name=3b00b2198d
FYI, this ptest failure also observed in yocto-3.1.10.rc1 release.
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2325/steps/12/logs/stdio qemux86-64-ptest fedora31-ty-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2396/steps/12/logs/stdio qemux86-64-ptest debian10-ty-2
This ptest is passing in yocto-3.1.11.rc2 release
*** Bug 14633 has been marked as a duplicate of this bug. ***
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/2635/steps/12/logs/stdio
Could be that it's not happening since we reduced the load average but not happening now.