-
Notifications
You must be signed in to change notification settings - Fork 12
[Feature]: tests take a long time to run locally #449
Comments
Looks like Also adding here - SpikeInterface recently started using a fancy module-based approach to triggers: https://github.com/SpikeInterface/spikeinterface/blob/master/.github/workflows/full-test.yml#L85-L118 Would be cool if we could do something similar, and changes to things like documentation or changes to differing modalities (an ophys interface vs an ecephys interface) need not trigger tests that only cover things untouched by those changes. Though for safety, should still have daily runs of the full test suite. |
Here is a table of the 100 longest test by duration as they stand now. Organized from the longest to the shortest: As @CodyCBakerPhD says, some of the biggest culprits are the large (non-unit) tests from the spikeinterface module. There are other large tests like It seems that making the first 10 tests faster would reduce the total time for local tests greatly as they account for 60 % of the total time.
|
What would you like to see added to nwb-conversion-tools?
Especially the ones in test_move_utils. Can we make these faster?
Is your feature request related to a problem?
No response
What solution would you like?
Especially the ones in test_move_utils. Can we make these faster?
Do you have any interest in helping implement the feature?
No.
Code of Conduct
The text was updated successfully, but these errors were encountered: