Resolve CI timeouts and miscellaneous updates for 2026-W35 - #66
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #66 +/- ##
==========================================
- Coverage 95.91% 95.90% -0.02%
==========================================
Files 69 69
Lines 3353 3366 +13
==========================================
+ Hits 3216 3228 +12
- Misses 137 138 +1
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Around 2026-05-31 (see here), CI jobs began to fail by timing out at the 6-hour limit. Previously (e.g. here) all jobs ran in 5–10 minutes.
This PR and branch are to diagnose and resolve the issue.
Actual steps:
timing out. Specifically, the case that calls the
tag_listCKAN API endpoint on the TDCI CKAN 'dev' instance times out. I did not investigate whether this happens because of slowness on the server side; a very large response (that never completes?); or some client-side issue in processing a complete response. The test case is skipped.Update hashes for known files.
Update the Zenodo record (DOI 10.5281/zenodo.14913729) with newer files.
Handle changes in the file format. Previously, the footer of each sheet contained 2 rows/cells like:
Recent files have instead:
Now, instead of removing a fixed number of footer rows, a regular expression is added to match and discard these entries. This regex handles both the old and new style.
Some ideas that were not tried in this PR:
PR checklist
Update documentationNo changes to behaviour.