-
Notifications
You must be signed in to change notification settings - Fork 699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed in Making test #381
Comments
You need to pass "-DPISTACHE_BUILD_TESTS=true" to cmake. I use the following script and "make test" works fine for me:
|
I got the following Test project /mnt/c/HAPPS/CTHINGS/CLIB/pistache 0% tests passed, 20 tests failed out of 20 Total Test time (real) = 0.39 sec The following tests FAILED: |
Try adding '-DPISTACHE_BUILD_EXAMPLES=true' to your invocation of cmake. // build pistache. Did you follow the official build instructions? They are right there, in the "readme.md" file, on the home page for this github repo (although you have to splice this together yourself. I should update the readme): cd pistache I assure you that the tests compile and run. This github repo is also configured to run them via travis-ci as a pre-submit check for every pull request. The bash script above that I use works fine on Gentoo Linux. Which Linux distro are you using? |
Using the Ubuntu Bash on Windows 10.... |
I've never gotten the tests to run correctly with "cmake -G "Unix Makefiles" -DPISTACHE_BUILD_EXAMPLES=true -DPISTACHE_BUILD_TESTS=true .. I've always had to insert "make -j 4" in between those two commands, otherwise I get errors similar to #249 . Definitly suggest checking that thread out and trying the things in there. |
#249 is a really old bug (relatively), and was created before the readme file was updated. I do not have Windows-10 to test on. The script that I posted above works fine for both Gentoo and Ubuntu 18. As for some tests passing and some failing.. yes, the tests are flakey, mostly due to TCP port re-use issues. Do you have any other processes on your Linux system that are binding the TCP ports used by the unit tests? Do this:
|
make test failing
make: *** No rule to make target 'test'. Stop....
The text was updated successfully, but these errors were encountered: