You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Test failure provides insufficient logging. Any suggestion as to how the Makefile or other scripts could be modified to produce useful logging would be much appreciated.
This issue is related to #1846, but this issue is asking for better logging, and using the windows tests as an example for reproducing broken tests, whereas #1846 is asking for a solution to the broken tests.
To Reproduce
Build via MSYS-2 using the below build yml. Below is the log, which is not very useful.
Sorry i missed that you had already worked on a windows build workflow. But i noticed also that logging on failure would be very nice, i did .. || (cat tests/*.log; exit 1) when i was iterating on it.
Describe the bug
Test failure provides insufficient logging. Any suggestion as to how the Makefile or other scripts could be modified to produce useful logging would be much appreciated.
This issue is related to #1846, but this issue is asking for better logging, and using the windows tests as an example for reproducing broken tests, whereas #1846 is asking for a solution to the broken tests.
To Reproduce
Build via MSYS-2 using the below build yml. Below is the log, which is not very useful.
Expected behavior
Test failure should provide some useful output, at least for the first failure, if not for all fails. At the least:
It's also not clear whether NO_VALGRIND in the Makefile is doing anything at all.
Environment (please complete the following information):
Additional context
see below YML (modified from the the non-working one that is in the repo):
The text was updated successfully, but these errors were encountered: