You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem is that many build envs are intentionally cut off from public network.
It would be good provide cmake option allowing extract test data from provided tar ball.
The text was updated successfully, but these errors were encountered:
You can add -DDOWNLOAD_TEST_DATA=OFF to your cmake command to prevent this issue. The tests should then be run like this (adding -LE NEEDS_DATA to the ctest command) to avoid any tests that require said data.
Your suggested addition of functionality to the cmake system is an elegant solution too though. It would be added around this part of the cmake system. With newer versions of cmake this can be handled far more easily. Implementing the functionality in a manner that is compatible with cmake version 3.11 is a little trickier, but not too bad. A pull request for that is welcome. I'm happy to provide some pointers if required.
You can add -DDOWNLOAD_TEST_DATA=OFF to your cmake command to prevent this issue
Wit that allmost all tests are afailing.
The tests should then be run like this (adding -LE NEEDS_DATA to the ctest command) to avoid any tests that require said data.
And by this only most of the test units are disabled.
Instead implemeting downloadiung those test data IMO those data instead be maintained in separated git repo should be part of thos repo and distributed/tagged with all stupp which depends on those data.
All this effort is only to reduce size of the dist data. IMO all that is pointless and only complicates whole process.
Problem is that many build envs are intentionally cut off from public network.
It would be good provide cmake option allowing extract test data from provided tar ball.
The text was updated successfully, but these errors were encountered: