--- Comment #5 from Fabio Valentini <decathorpe(a)gmail.com> ---
It already printed the summary. All tests passed and 3 were skipped.
How would you know which test got a UD?
The problem is that if a test crashes instead of reporting failure, it will not
be listed, since the test runner can't report back.
You can try running tests with "--test-threads 1" to make things run
sequentially, and then it should be obvious which test's thread crashed the
I tried reproducing the failure locally from a source checkout, and the only
test (other than the "new_type" doctests failures) is:
This might or might not be the failure that causes the SIGILL in your case.
I also noticed that the upstream project was officially abandoned last month :(
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component