Some unit tests fail when logging messages on Windows / MinGW64
A Windows / MinGW64 user sees the following errors in the unit tests:
circuit_timeout: [forking] Nov 03 15:52:03.329 [err] tor_asprintf(): Bug: Internal error in asprintf (on Tor 0.2.9.4-alpha-dev 8f465808a06c739d)
Nov 03 15:52:03.329 [err] tor_assertion_failed_(): Bug: compat.c:515: tor_asprintf: Assertion 0 failed; aborting. (on Tor 0.2.9.4-alpha-dev 8f465808a06c739d)
Nov 03 15:52:03.329 [err] Bug: Assertion 0 failed in tor_asprintf at compat.c:515. (Stack trace not available) (on Tor 0.2.9.4-alpha-dev 8f465808a06c739d)
OK
rend_fns: [forking] OK
geoip: Nov 03 15:52:11.920 [err] tor_asprintf(): Bug: Internal error in asprintf (on Tor 0.2.9.4-alpha-dev 8f465808a06c739d)
Nov 03 15:52:11.920 [err] tor_assertion_failed_(): Bug: compat.c:515: tor_asprintf: Assertion 0 failed; aborting. (on Tor 0.2.9.4-alpha-dev 8f465808a06c739d)
Nov 03 15:52:11.920 [err] Bug: Assertion 0 failed in tor_asprintf at compat.c:515. (Stack trace not available) (on Tor 0.2.9.4-alpha-dev 8f465808a06c739d)
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
make: *** [test] Error 3https://trac.torproject.org/projects/tor/attachment/ticket/20530/test-output-fmp.txt
Split off from #20530 (moved). This is probably happening due to #19999 (moved).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information