Skip to content
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 broken? #22

Open
Seegras opened this issue Nov 21, 2016 · 2 comments
Open

tests broken? #22

Seegras opened this issue Nov 21, 2016 · 2 comments

Comments

@Seegras
Copy link

Seegras commented Nov 21, 2016

trying to make debian packages with dh_make results in it being unable to compile the test-cases. I suspect they are broken:

12 FAILED TESTS
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 0.01 sec
The following tests FAILED:
1 - gtest-LoadTest (Failed)
Errors while running CTest
Makefile:130: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory '/usr/src/git/libfunctionality/obj-x86_64-linux-gnu'
dh_auto_test: make -j1 test ARGS+=-j1 returned exit code 2
debian/rules:18: recipe for target 'binary' failed

if they're broken, they should be either removed or fixed.

@rpavlik
Copy link
Member

rpavlik commented Jul 14, 2018

Hmm, sorry I missed this earlier. I was pretty sure that the Sensics CI had been building and running the tests on Windows and Linux, but clearly something was wrong if they failed for you. I'll look into it.

By any chance, do you have your progress on making a package available somewhere? I was intending to do that too.

@rpavlik
Copy link
Member

rpavlik commented Jul 16, 2018

OK, I looked into this. Looks like it's actually an rpath issue - we aren't using any particular search path in libfunctionality beyond just calling dlopen, so the test failures are because it can't find the dummy plugin that it wants.

I'm not sure what happened to make it fail now when it worked for me before, I'm assuming the rpath behavior of CMake must have changed. (I tried a very old commit, and it was broken there too even though a commit said "fix linux tests"... suggesting it's the environment not the code itself)

The code does actually work correctly, it's the tests that are faulty.

Bumping from the 1.0 project.

rpavlik added a commit that referenced this issue Jul 16, 2018
Temporary (should just fix their creation/invocation),
related to #22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants