test(airflow): isolate yield_pipeline_status tests from SQLAlchemy registry pollution

[IceS2]

Problem

tests/unit/airflow/test_airflow_metadata.py::TestYieldPipelineStatus::{test_uses_start_date_when_logical_date_is_none, test_skips_run_when_both_dates_are_none} intermittently fail in CI (e.g. on #28977) with:

dag_run = MagicMock(spec=DagRun)
...
sqlalchemy.exc.InvalidRequestError: One or more mappers failed to initialize -
can't proceed with initialization of other mappers.
Triggering mapper: 'Mapper[DagWarning(dag_warning)]'.
Original exception was: 'NullType' object has no attribute 'length'

Root cause

Building MagicMock(spec=DagRun) makes unittest.mock walk dir(DagRun). DagRun's association proxies resolve through orm.class_mapper(), which calls _check_configure() → _configure_registries({registry}, cascade=True) — i.e. configuring the entire shared SQLAlchemy mapper registry just to build the mock.

If any other test scheduled on the same pytest -n auto worker has already left a mapper in a failed state (here airflow's DagWarning mapper, marked _configure_failed), that cascade re-raises and these two tests fail — even though the failure has nothing to do with the date-fallback logic they verify.

Because xdist work distribution shifts with the overall test corpus, the two tests fail on some PRs (#28977) and pass on others (#28991) despite identical base — which reads as flakiness. The tests pass in isolation and when their file is run alone.

Fix

Build the fake DagRun with types.SimpleNamespace carrying exactly the attributes yield_pipeline_status reads (run_id, dag_id, state, logical_date, start_date). It never introspects DagRun, so it cannot trigger mapper configuration, and — being a real object — still raises AttributeError on unexpected attribute access, preserving the typo-safety spec= gave.

Test-only change; the 16 tests in the file pass unchanged.

[github-actions]

❌ PR checklist incomplete

This PR cannot be merged until the following are addressed on its linked issue:

• No GitHub issue is linked. Link an issue in the Development section of the PR (or add Fixes #12345 to the description). For a same-org cross-repo issue, add Fixes open-metadata/<repo>#123 to the description.

The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically.

Maintainers can bypass this check by adding the skip-pr-checks label.

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ingestion'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🟡 Playwright Results — all passed (13 flaky)

✅ 4291 passed · ❌ 0 failed · 🟡 13 flaky · ⏭️ 88 skipped

Shard	Passed	Failed	Flaky	Skipped
✅ Shard 1	301	0	0	4
🟡 Shard 2	811	0	1	9
🟡 Shard 3	809	0	3	8
🟡 Shard 4	848	0	2	12
🟡 Shard 5	733	0	1	47
🟡 Shard 6	789	0	6	8

🟡 13 flaky test(s) (passed on retry)

• Features/DataQuality/ColumnLevelTests.spec.ts › Column Values To Not Match Regex (shard 2, 1 retry)
• Features/IncidentManager.spec.ts › Resolving incident & re-run pipeline (shard 3, 1 retry)
• Features/RTL.spec.ts › Verify Following widget functionality (shard 3, 1 retry)
• Features/Table.spec.ts › Table pagination with sorting should works (shard 3, 1 retry)
• Flow/PersonaFlow.spec.ts › Set default persona for team should work properly (shard 4, 1 retry)
• Pages/CustomProperties.spec.ts › Hyperlink (shard 4, 1 retry)
• Pages/ExplorePageRightPanel_KnowledgeCenter.spec.ts › Should remove user owner for knowledgeCenter (shard 5, 2 retries)
• Pages/Lineage/LineageFilters.spec.ts › Verify lineage service type filter selection (shard 6, 1 retry)
• Pages/Lineage/LineageFilters.spec.ts › Verify lineage schema filter selection (shard 6, 1 retry)
• Pages/Lineage/LineageRightPanel.spec.ts › Verify custom properties tab IS visible for supported type: searchIndex (shard 6, 1 retry)
• Pages/Lineage/PlatformLineage.spec.ts › Verify domain platform view (shard 6, 1 retry)
• Pages/LogsViewer.spec.ts › Logs page shows breadcrumb, summary, and log viewer or empty state after opening from bundle suite pipeline tab (shard 6, 1 retry)
• Pages/Users.spec.ts › Admin soft & hard delete and restore user (shard 6, 1 retry)

📦 Download artifacts

How to debug locally

# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace

[gitar-bot]

Code Review ✅ Approved

Replaces MagicMock with SimpleNamespace in yield_pipeline_status tests to prevent SQLAlchemy mapper registry pollution. This change eliminates intermittent CI failures caused by cross-test dependency on registry configuration.

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}