kevinkreiser/prime_server

Error on make test

ismailsunni opened this issue · 4 comments

I followed the step in the README,

Everything is fine until the make test -j8. Here is the error message:

make[1]: Leaving directory '/home/ismailsunni/dev/cpp/prime_server'
make  check-TESTS
make[1]: Entering directory '/home/ismailsunni/dev/cpp/prime_server'
make[2]: Entering directory '/home/ismailsunni/dev/cpp/prime_server'
PASS: test/zmq
./test-driver: line 107: 34739 Alarm clock             "$@" > $log_file 2>&1
FAIL: test/interrupt
./test-driver: line 107: 34734 Alarm clock             "$@" > $log_file 2>&1
FAIL: test/shaping
./test-driver: line 107: 34725 Alarm clock             "$@" > $log_file 2>&1
FAIL: test/http
./test-driver: line 107: 34726 Alarm clock             "$@" > $log_file 2>&1
FAIL: test/netstring
============================================================================
Testsuite summary for prime_server 0.7.0
============================================================================
# TOTAL: 5
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  4
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
Please report to https://github.com/kevinkreiser/prime_server/issues
============================================================================
make[2]: *** [Makefile:1330: test-suite.log] Error 1
make[2]: Leaving directory '/home/ismailsunni/dev/cpp/prime_server'
make[1]: *** [Makefile:1438: check-TESTS] Error 2
make[1]: Leaving directory '/home/ismailsunni/dev/cpp/prime_server'
make: *** [Makefile:1673: check-am] Error 2

Is it normal?

My environment is Ubuntu 20.04

Thanks :)

try with just make test adding -j8 tell its it run up to 8 of them at the same time which can take a long time if you dont actually have a decent CPU.

Thanks, @kevinkreiser for the reply.
I tried to run make test only, but I still got the same issue. I also tried with -j4 and -j6. Both also gave the same issue.

My CPU is Intel® Core™ i7-8550U CPU @ 1.80GHz × 8 (XPS 13). Perhaps it's not decent enough?

@ismailsunni try this, go into each test and increase the alarm threshold to a large number and let it run.

https://github.com/kevinkreiser/prime_server/blob/master/test/http.cpp#L529

are these tests really running for 5 minutes on your end before failing? your clock speed seems pretty slow but still i wouldnt expect them to take 5 minutes. on my beast mode ryzen cpu they take 15 seconds each, on CI inside a VM they take about a minute each. the alarms are there because when there is a bug in the code the most likely thing is that the tests dont finish because the threads join forever waiting for the last request or response that was never sent or received

also what OS are you on and what version of zeromq do you have