search

norlab-ulaval / libnabo

A fast K Nearest Neighbor library for low-dimensional spaces
http://norlab-ulaval.github.io/libnabo/
BSD 3-Clause "New" or "Revised" License
438 stars 143 forks source link

Transition to gtest #6

Closed simonlynen closed 9 years ago

simonlynen commented 10 years ago

Transitioning to gtests would allow build-server integration for test-results.

stephanemagnenat commented 10 years ago

That is a good point. On the other hand, it is an added dependency. Currently libnabo uses CTest. Isn't that a CTest integration for the build server?

simonlynen commented 10 years ago

yes, I would need some type of file exported with the results (such as TAP) which I can parse. After a quick glance I couldn't find something like this here: http://www.cmake.org/cmake/help/v2.8.8/ctest.html . Do you have a better pointer for me?

simonlynen commented 10 years ago

This might be useful: http://stackoverflow.com/questions/6329215/how-to-get-ctest-results-in-hudson-jenkins

stephanemagnenat commented 10 years ago

Yes this seems the right starting point. I do not really have time to work on that now, should we delay that until there is a PhD student working on TRADR? (the project that is likely to use massively libpointmatcher, and therefore libnabo)

stephanemagnenat commented 10 years ago

This file https://bitbucket.org/shackra/ctest-jenkins/downloads/ctest-xunit.zip seems the thing to use. Practically, should we add something to libnabo or only to the Jenkins side?

simonlynen commented 9 years ago

Not needed anymore since we have ctest integration with the build-server now. http://129.132.38.183:8080/job/libnabo/lastCompletedBuild/testReport/