Skip/Speed up tests, resolve most open issues#67
Conversation
…, breaking 4 second data
|
@mdavis-xyz thank you for the PR (and all the other issues and PRs). This has spurred me into properly fixing the test suite so it can run in seconds not hours, and then setup cicd. Once that is done we can rebase this branch to include the fixed and complete tests. Then push on and merge. Thanks for your patience! |
|
@mdavis-xyz I've created a bit of a headache by changing the test frame work while this PR is inflight. To save you the messy rebase and to expedite getting this changes on to main I'm going to go ahead and cherry pick, PR, and review the feature changes one at time. Any that I'm unsure about I'll leave as open PRs where we can continue to iterate/discuss. |
Heads-up on PR #67Hey Matt — thanks again for PR #67. We've broken it into ~10 smaller, individually reviewable PRs against Hopefully, with better testing setup we can have a more sane development and review process going forward :) What landed (in order)
Calls we made that deviate from your code
Bugs in your code we fixed during cherry-pick(Not blockers — just want you to see them so you're not surprised.)
What we'd love your eye on
|
I've had some issues open for a while. As discussed, it's hard to merge them confidently, given that the tests take half a day, and some functionality has broken due to changes to nemweb.
So I've worked to streamline the tests and the code itself. Now a test with an empty cache takes 2h30m. It's 1h40m with a full cache.
Some of the tests, I just skipped. I normally hate it when people do that. Although for now, I think it's worth doing temporarily, so that we can check all these other bug fixes and feature additions.
This fixes:
And I include some currently open pull requests:
I know it's bad style to combine so many unrelated issues into one pull request. However given that the master branch is not easily buildable, some of these do work together. Look through this pull request one commit at a time, if you want to see review each change separately.
Aside from the tests now skipped with
@unittest.skip(), all unit tests pass.I increased the minimum Python version to 3.10, from 3.9, because
uvcomplained about a dependency. 3.9 is now deprecated, so I think this is ok.