Replies: 1 comment
|
Shelving this for now -- not implementing. It's almost purely upstream-parity: Archiving the plan sketch for whenever this thaws:
Revisit if a future #227 round shows the counts growing or a real consumer asks. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
#227 round 3: the six names from #237 are all shipped and their error classes are at ZERO across the matrix. What remains (s2
unit/modelssetup errors):Cases:
testing_teamnot found -- 4 (3.1.0), 4 (3.1.8), 21 (3.2.2), 41 (3.3.1), 41 (3.4.0.dev). The multi-team fixture upstream added in the 3.3 era; the count doubles at 3.3+ and this is now the largest missing-fixture class. E.g.test_trigger.py::test_trigger_team_name_stored,test_variable.py::TestVariable::test_set_variable_sets_teammock_supervisor_commsnot found -- 3 flat on 3.2+. E.g.test_xcom.py::TestXCom::test_set_serialize_call_current_signaturereset_logging_config/clean_executor_loader-- 1-2 each, tests_common-internal plumbing; IMO out of scope, listing for completenessLogs here. CC #227, successor to #237
All reactions