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

Last batch of critical funcgen datachecks #76

Merged
merged 7 commits into from
Feb 1, 2019

Conversation

james-monkeyshines
Copy link
Contributor

Also added a new core datacheck for analysis descriptions, which I realised we needed after looking at the funcgen version of the same datacheck.

James Allen added 7 commits January 31, 2019 12:34
…n, not just a subset. But not there yet, so have an interim datacheck to cover the same subset as existing healthcheck.
…n, not just a subset. But not there yet, so have an interim datacheck to cover the same subset as existing funcgen healthcheck.
…datacheck was generalised and renamed 'DataFilesExist'
…s always run, regardless of whether the data in the tables has changed. An example of case that needs this is the one that checks funcgen data files - there is an external dependency there, on the data file directory. We don't know if that has changed, so always need to run the test, just in case.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 328

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 98.777%

Totals Coverage Status
Change from base Build 325: 0.0%
Covered Lines: 1696
Relevant Lines: 1717

💛 - Coveralls

@thomasmaurel thomasmaurel merged commit a749b5c into master Feb 1, 2019
@thomasmaurel thomasmaurel deleted the feature/funcgen_datachecks branch February 1, 2019 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants