Closed XVilka closed 3 years ago
Huh, odd. Is the file created anyway? e.g. try listing C:\projects\rizin\build\meson-logs\
in the build runner.
Ok, just recreated an error in a custom PR and listed log files:
Full log written to C:\projects\rizin\build\meson-logs\testlog.txt
dir C:\Projects\rizin\build\meson-logs
Volume in drive C has no label.
Volume Serial Number is 0CA6-1C58
Directory of C:\Projects\rizin\build\meson-logs
08/31/2021 05:25 AM <DIR> .
08/31/2021 05:25 AM <DIR> ..
08/31/2021 05:25 AM 42,889 install-log.txt
08/31/2021 05:14 AM 176,636 meson-log.txt
08/31/2021 05:25 AM 1,764,002 testlog.json
08/31/2021 05:25 AM 34,323 testlog.junit.xml
08/31/2021 05:25 AM 602,866 testlog.txt
5 File(s) 2,620,716 bytes
2 Dir(s) 67,561,287,680 bytes free
type C:\Projects\rizin\build\meson-logs\testlog.txt
Log of Meson test suite run on 2021-08-31T05:25:45.102936
Inherited environme
Then I print the whole of the testlog.txt
and it's looong, here are the lines that reported on other systems:
iles\CMake\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\LLVM\bin;C:\Tools\vcpkg;C:\Tools\Coverity\bin;C:\Program Files (x86)\NSIS;C:\Tools\Octopus;C:\Program Files\Meson\;C:\Program Files (x86)\Apache\Maven\bin;C:\Tools\GitVersion;C:\Users\appveyor\AppData\Local\Microsoft\WindowsApps;C:\Users\appveyor\.dotnet\tools;C:\Users\appveyor\AppData\Roaming\npm;C:\Users\appveyor\AppData\Local\Yarn\bin;C:\Program Files\AppVeyor\BuildAgent\;C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\Llvm\x64\bin;C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja;C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\Linux\bin\ConnectionManagerExe C:\projects\rizin\build\test/unit\test_vector.exe
----------------------------------- output -----------------------------------
Gillian Seed: 1630387552
test_vector_init OK
test_vector_new OK
test_vector_fini ERR
[XX] Fail at line 75: init len: expected 6, got 1.
test_vector_clear OK
test_vector_free OK
test_vector_clone OK
test_vector_empty OK
test_vector_remove_at OK
test_vector_remove_range
See https://ci.appveyor.com/project/rizinorg/rizin/builds/40584734/job/gefpw4225gtlyi56#L3474
Any updates on this one? Let me know if you need more information.
I just went and actually looked into it.
This is an intentional behavior change in commit bb9d8b5b80e5f4aa421b4ad549d71fd103f2b1dc.
You are NOT using the same version of meson on both systems -- or at least you are not using meson 0.59.1 on one of them. :)
Also, I just noticed you are running ninja test
on Linux, and meson test
on Windows. The former invokes meson test --print-errorlogs
but you did not add that --print-errorlogs option to the Windows invocation.
Describe the bug The same Meson configuration and command line prints the output of failed unit tests on
meson test -C build
orninja -C build test
on any *nix systems - Linux, FreeBSD, OpenBSD, NetBSD, etc. At the same time it fails to do so on Windows systems. It should do that consistently on all supported systems.On Linux:
On Windows:
To Reproduce
meson test
: test/unit/*Expected behavior The same output on any system:
system parameters
.appveyor.yml
for all detailsSee https://github.com/rizinorg/rizin/issues/1556