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

incompatible code for vmtk testing? #1

Open
deniskristak opened this issue Sep 16, 2021 · 1 comment
Open

incompatible code for vmtk testing? #1

deniskristak opened this issue Sep 16, 2021 · 1 comment

Comments

@deniskristak
Copy link

deniskristak commented Sep 16, 2021

hello..
ive been trying to run tests against vmtk 1.4...
ive switched to vmtk 1.4 tag, installed it from source, including the cmake flag -DVMTK_BUILD_TESTING=ON, then, in github repo, followed into folder tests and vmtk-test-data, pulled this commit and ran tests, here's what i am getting (log is too long to paste here, i'll attach pastebin link https://pastebin.com/ebg806Tb
i think maybe those tests aren't compatible with vmtk 1.4 (even though on github they link to each other)?
is there any other commit of vmtk-test-data which you suppose should work for vmtk 1.4?
thanks a lot

@kayarre
Copy link
Contributor

kayarre commented Dec 7, 2021

I currently run the tests from the build directory as they are copied there in the build process It does not sound like that is what you are doing. It very well may not be finding the correct data locations.

From what I can tell cmake calls git init during the build process and does a checkout of the submodule commit which would override manual check out of a specific tag ( Until this commit #391 ). I have not looked at v1.4 release setup, but my suspicion is something along those lines is happening. Is there a specific reason to use the v1.4 release versus the master branch if you are already building from source?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants