Not sure how to read this log and identify what is wrong here. ``` 91 oeqa.utils.subprocesstweak.OETestCalledProcessError: Command '['wine', 'cmd', '/c', 'W:\\testimage-sdk\\environment-setup-core2-64-poky-linux.bat', '>', 'NUL', '&&', '%CC%', '-c', '-g', 'test.c', '-o', 'test.o']' returned non-zero exit status 49 92 Standard Output: wine: failed to map the shared user data: c0000018 93 Can't recognize 'x86_64-poky-linux-gcc -m64 -march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=W:\TEST~Y0Z\sysroots\core2-64-poky-linux -c -g test.c -o test.o' as an internal or external command, or batch script. 94 ... 109 RESULTS - binutils.BinutilsTest.test_ranlib: ERROR (1.14s) ```
meta-mingw ubuntu2004-vk-3 master completed at 2025-03-06T01:16:19Z https://autobuilder.yoctoproject.org/valkyrie/#/builders/7/builds/1162/steps/17/logs/stdio
May be due to rare address randomization issue.
Richard is triggering a build on a 20.04 worker to see if this can happen on demand.
Newer versions of wine might RLIMIT_AS to unlimited , which disables ASLR on i386. In local testing, 20.04 appears to ship with wine 5.0. We should verify the version on the AB, and then also verify if the RLIMIT_AS is set in that version. If not, we might be able to force it when running older wine
Re-open if it happens again. We don't hove ubu 20.04 workers anymore.