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

[Feature]: Test read of dandisets systematically in CI #1804

Open
3 tasks done
rly opened this issue Dec 14, 2023 · 0 comments
Open
3 tasks done

[Feature]: Test read of dandisets systematically in CI #1804

rly opened this issue Dec 14, 2023 · 0 comments
Labels
category: enhancement improvements of code or code behavior priority: low alternative solution already working and/or relevant to only specific user(s) topic: testing issues related to testing

Comments

@rly
Copy link
Contributor

rly commented Dec 14, 2023

What would you like to see added to PyNWB?

Follow-up to #1794

It would be ideal if in the CI of this repo or in a separate repo like https://github.com/dandi/dandisets-healthstatus, we test reading of NWB files from dandisets using the latest commit of pynwb. Given limits on CI runtime, we have to split these checks into batches. Currently the batches are decided randomly but that means the tests can pass simply due to bad luck. We should test systematically instead of randomly, e.g., scan through dandisets 000001-000100 on monday, 000101-000200 on tuesday, etc.

Separately but relatedly, it would be nice if we could create copies of nwb files on dandi but without the bulk array data (datasets with size above some threshold). The files would be significantly smaller, and it would be significantly faster to test. Similar to https://github.com/bids-standard/bids-examples

Is your feature request related to a problem?

No response

What solution would you like?

See above.

Do you have any interest in helping implement the feature?

Yes.

Code of Conduct

@rly rly added category: enhancement improvements of code or code behavior topic: testing issues related to testing priority: low alternative solution already working and/or relevant to only specific user(s) labels Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: enhancement improvements of code or code behavior priority: low alternative solution already working and/or relevant to only specific user(s) topic: testing issues related to testing
Projects
None yet
Development

No branches or pull requests

1 participant