-
Notifications
You must be signed in to change notification settings - Fork 26
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
Expose number of jobs to organize #1341
Expose number of jobs to organize #1341
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1341 +/- ##
==========================================
+ Coverage 88.88% 89.03% +0.14%
==========================================
Files 76 76
Lines 10240 10243 +3
==========================================
+ Hits 9102 9120 +18
+ Misses 1138 1123 -15
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
more info on segfault? I usually try to run those through valgrind to get a sense where/why might be happening although IIRC it was tricky with python stuff. re tests - just make one of the invocations in dandi/tests/test_organize.py with |
Sadly no. It was just something random that occurred in certain user environments during first round of alpha testing - the local traceback led back to |
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
🚀 PR was released in |
Recent usage of the DANDI API in the NWB GUIDE revealed a sporadic
joblib
issue that results in segmentation faults - no clue what actually causes it for some users, but the best solution we have for now is to just expose job usage directlyWhere should tests for this go?