potiuk commented on code in PR #46891:
URL: https://github.com/apache/airflow/pull/46891#discussion_r2203526743
##########
airflow-core/tests/unit/api_fastapi/core_api/routes/public/test_plugins.py:
##########
@@ -33,29 +33,20 @@ class TestGetPlugins:
# Filters
(
{},
- 13,
+ 4,
[
"MetadataCollectionPlugin",
- "OpenLineageProviderPlugin",
- "databricks_workflow",
"decreasing_priority_weight_strategy_plugin",
- "edge_executor",
- "hive",
- "plugin-a",
- "plugin-b",
- "plugin-c",
- "postload",
"priority_weight_strategy_plugin",
- "test_plugin",
"workday_timetable_plugin",
],
),
(
{"limit": 3, "offset": 2},
- 13,
- ["databricks_workflow",
"decreasing_priority_weight_strategy_plugin", "edge_executor"],
+ 4,
+ ["priority_weight_strategy_plugin",
"workday_timetable_plugin"],
Review Comment:
This is more of an experiment - I an trying to remove FAB remnants from some
of the tests. In main, we seem to have a few FAB-bound plugins (i.e. adding
views) that are currently required and expected by the "core tests" - but since
Python 3.13 does not have FAB, those tests fail - moslty during import and some
during runtime execution of tests. So what I am trying to do in the last few
iterations is to move "fab"-related tests to "fab" provider (even if they are
testing "plugins" APIs or "plugins manager" - when they expect FAB-related
plugins to work. Still not complete but it's a good thing to do to 'truly"
isolate FAB from core. Currently there are a number of tests that implicitly
assume FAB is installed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
