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/cmake external data #1251

Closed

Conversation

theodelrieu
Copy link
Contributor

@theodelrieu theodelrieu commented Sep 20, 2018

This PR solves #1185 and affiliates, by putting every data file (test and benchmarks) somewhere else (currently one of my repositories...), and fetching them with CMake ExternalData module.

The current repo size is 22MB, down from more than 150MB.

There are more than 1K files to download when running tests, which is a bit annoying. The CI will most likely be slower.

We could refactor the tests/cmake files and dedicate a specific CI job for tests requiring data files, and only trigger the 1K download when launching those specific tests.

Last but not least, we have to decide where to store those files.

Let me know what you think!

Pull request checklist

Read the Contribution Guidelines for detailed information.

  • Changes are described in the pull request, or an existing issue is referenced.
  • The test suite compiles and runs without error.
  • Code coverage is 100%. Test cases can be added by editing the test suite.
  • The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header file single_include/nlohmann/json.hpp. The whole process is described here.

@theodelrieu
Copy link
Contributor Author

Well, CI jobs timed out...

@chuckatkins
Copy link
Contributor

fwiw at kitware we're beginning to transition away from ExternalData in favor of git-lfs. It's got it's own pluses and minuses but the broader git community as a whole seems to be moving that way. Just something to consider...

@theodelrieu
Copy link
Contributor Author

This could be a great alternative indeed, I'll try to find some time to take a look.

@stale
Copy link

stale bot commented Nov 4, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Nov 4, 2018
@stale stale bot closed this Nov 11, 2018
@theodelrieu theodelrieu deleted the tests/cmake_external_data branch March 13, 2019 08:45
@nlohmann nlohmann mentioned this pull request May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants