-
Notifications
You must be signed in to change notification settings - Fork 1k
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
tests: Works on travis, fails on my buildbox. #232
Comments
After porting the tests to cppunit I can run the tests on my native, Fedora without any hypervisor layer. Same results, slightly better formatted:
It's a bit unfortunate that the delays are random and thus not possible to reproduce. |
The tests are broken since they assume that for example The tests needs to be patched taking the actual, elapsed time into account rather than blindly trusting usleep() EDIT: typos |
Use the cpppunit test framework instead og catkin. This means that the dependency on both catkin and boost can be dropped to run the tests. The timer tests are patched to fix the problem described in wjwwood#232. The new tests needs c++11 chrono features.
Attaching updated tests, These are cppunit tests, not directly usable in current, catkin context. They also relies on C++11, which somehow makes the timer tests obsolete (since C++11 has platform-indepented timers built in). Nevertheless, enclosed tests works on both Linux and Macos, basically validating the pre-C++11 code with C++11 primitives. |
Compute actually elapsed time instead of assuming that usleep() sleeps for exactly the right time, which isn't guaranteed.
Compute actually elapsed time instead of assuming that usleep() sleeps for exactly the right time, which isn't guaranteed.
Compute actually elapsed time instead of assuming that usleep() sleeps for exactly the right time, which isn't guaranteed.
Compute actually elapsed time instead of assuming that usleep() sleeps for exactly the right time, which isn't guaranteed.
Compute actually elapsed time instead of assuming that usleep() sleeps for exactly the right time, which isn't guaranteed.
Compute actually elapsed time instead of assuming that usleep() sleeps for exactly the right time, which isn't guaranteed.
This is really about the #231 PR. However, since the current master doesnt build, there is no way to reproduce test errors there.
On #231, commit 6dd5782, the run_tests completes successfully on travis. However, on my local test box the same test fails, with lots of messages like
My local box is pretty fast, a Ryzen 7 gen3. OTOH, the Debian machine I use for testing is a vm under VirtualBox.
But then again, I guess the travis build also runs on a vm.
The text was updated successfully, but these errors were encountered: