Test failure for SRFI-114 comparators on 0.6.5
On ArchLinux x86_64 the test phase of the compilation of release 0.6.5 fails due to:
%%%% Starting test SRFI-114 comparators
FAIL comparator? (default-comparator)
FAIL comparator-comparison-procedure? (default-comparator)
FAIL comparator-hash-function? (default-comparator)
# of expected passes 168
# of unexpected failures 3
Comments (5)
-
repo owner -
repo owner I've set up x64 Arch Linux (2015.06.01) but couldn't reproduce the issue. However I've got different test failure for process on both HEAD and 0.6.5.
This error only happens when I run
make test
butmake test-ext
which only executes extra module tests. -
Account Deleted Hello thank you. After your note I repeated the creation of the package and yes, everything is working (now!) and the tests are valid (all of them). As soon as I have some time I will investigate, I suspect that between my first note and your answer an update on some library fixed the problem. I counted 88 updates.to my system in this interval of time.
The funny thing is that I don't get any error not even on
make test-ext
:[andrea@dixie sagittarius-0.6.5]$ make test-ext Scanning dependencies of target test-ext testing extensions %%%% Starting test (run-crypto-test) # of expected passes 104 %%%% Starting test (run-ffi-test) # of expected passes 144 %%%% Starting test process tests # of expected passes 9 %%%% Starting test regular expression test # of expected passes 643 %%%% Starting test (run-socket-test) # of expected passes 51 %%%% Starting test (run-threads-test) # of expected passes 56 %%%% Starting test (run-time-test) # of expected passes 68 %%%% Starting test (run-zlib-test) # of expected passes 10 Built target test-ext
-
repo owner - changed status to resolved
Thank you for the mention. I'll close the issue for now.
-
repo owner The reason why I've got process test failed was because of my configuration of Arch Linux. I was lazy to setup swap area so just install everything in one partition. And I've allocated 2GB memory on my VM. However it seems running full test consumes more than 2GB memory so system couldn't allocate memory for
fork
(got errno12
). So allocating 4GB memory made test works.It might be better to separate tests into multiple process instead of one go to avoid memory shortage. (frequently occurs on Cygwin).
- Log in to comment
Thanks you for the report! I'll have look asap.