=?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org>, =?utf-8?q?Hervé?= Poussineau <hpous...@reactos.org> Message-ID: In-Reply-To: <llvm.org/llvm/llvm-project/pull/107...@github.com>
dpaoliello wrote: > I need a little bit help to understand why Linux buildbot succeeds, while > Windows one fails. Looks like an AV in some of the tests. If you open up [the log](https://buildkite.com/llvm-project/github-pull-requests/builds/98827#0191d356-ebb6-4489-b44b-11f711644a12) for the Windows build you can see things like: ``` FAIL: LLVM :: MC/Mips/forbidden-slot.s (35919 of 54904) ******************** TEST 'LLVM :: MC/Mips/forbidden-slot.s' FAILED ******************** Exit Code: 3221225477 Command Output (stdout): -- # RUN: at line 1 c:\ws\src\build\bin\llvm-mc.exe -assemble -mcpu=mips64r6 -arch=mips64el -filetype=obj C:\ws\src\llvm\test\MC\Mips\forbidden-slot.s -o tmp.o # executed command: 'c:\ws\src\build\bin\llvm-mc.exe' -assemble -mcpu=mips64r6 -arch=mips64el -filetype=obj 'C:\ws\src\llvm\test\MC\Mips\forbidden-slot.s' -o tmp.o # .---command stderr------------ # | PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace. # | Stack dump: # | 0. Program arguments: c:\\ws\\src\\build\\bin\\llvm-mc.exe -assemble -mcpu=mips64r6 -arch=mips64el -filetype=obj C:\\ws\\src\\llvm\\test\\MC\\Mips\\forbidden-slot.s -o tmp.o # | Exception Code: 0xC0000005 # | #0 0x00007ff657a1bc59 (c:\ws\src\build\bin\llvm-mc.exe+0x8abc59) # | #1 0x00007ff657a1cc49 (c:\ws\src\build\bin\llvm-mc.exe+0x8acc49) # | #2 0x00007ff657a1d86c (c:\ws\src\build\bin\llvm-mc.exe+0x8ad86c) # | #3 0x00007ff657a1d749 (c:\ws\src\build\bin\llvm-mc.exe+0x8ad749) # | #4 0x00007ff657a077e5 (c:\ws\src\build\bin\llvm-mc.exe+0x8977e5) # | #5 0x00007ff657a05d7e (c:\ws\src\build\bin\llvm-mc.exe+0x895d7e) # | #6 0x00007ff657a71fcc (c:\ws\src\build\bin\llvm-mc.exe+0x901fcc) # | #7 0x00007ff65717feb5 (c:\ws\src\build\bin\llvm-mc.exe+0xfeb5) # | #8 0x00007ff65718326b (c:\ws\src\build\bin\llvm-mc.exe+0x1326b) # | #9 0x00007ff657b77910 (c:\ws\src\build\bin\llvm-mc.exe+0xa07910) # | #10 0x00007ffad8a07ac4 (C:\Windows\System32\KERNEL32.DLL+0x17ac4) # | #11 0x00007ffae696a4e1 (C:\Windows\SYSTEM32\ntdll.dll+0x5a4e1) # `----------------------------- # error: command failed with exit status: 0xc0000005 -- ******************** ``` You can follow the instructions on the LLVM docs on how to run a single test: <https://llvm.org/docs/TestingGuide.html#unit-and-regression-tests> Assuming that you don't have `llvm-lit` on your path, you can run it like this: ``` python .\build\bin\llvm-lit.py -s -v .\llvm\test\MC\Mips\forbidden-slot.s ``` The test failure also shows the exact command that was run (in this case `c:\ws\src\build\bin\llvm-mc.exe -assemble -mcpu=mips64r6 -arch=mips64el -filetype=obj C:\ws\src\llvm\test\MC\Mips\forbidden-slot.s -o tmp.o`), so you can retry that under a debugger, assuming that you've [enabled debug symbols when building LLVM](https://llvm.org/docs/CMake.html#frequently-used-cmake-variables). https://github.com/llvm/llvm-project/pull/107744 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
