Skip to content

Run fab provider tests in v2-11-test#61633

Open
potiuk wants to merge 1 commit intoapache:v2-11-testfrom
potiuk:run-fab-provider-tests-in-v2-11-test
Open

Run fab provider tests in v2-11-test#61633
potiuk wants to merge 1 commit intoapache:v2-11-testfrom
potiuk:run-fab-provider-tests-in-v2-11-test

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Feb 8, 2026

Since we are releasing fab provider from v2-11-test we should also run fab provider tests there.


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Feb 8, 2026
@potiuk potiuk marked this pull request as draft February 8, 2026 11:34
@potiuk potiuk force-pushed the run-fab-provider-tests-in-v2-11-test branch 2 times, most recently from 540a862 to 38a9bf0 Compare February 8, 2026 17:12
@potiuk potiuk added the legacy api Whether legacy API changes should be allowed in PR label Feb 8, 2026
@potiuk potiuk force-pushed the run-fab-provider-tests-in-v2-11-test branch 3 times, most recently from d1428ac to d95280a Compare February 8, 2026 19:19
@potiuk potiuk marked this pull request as ready for review February 8, 2026 20:40
@potiuk potiuk force-pushed the run-fab-provider-tests-in-v2-11-test branch from d95280a to b7e059b Compare February 8, 2026 20:58
@potiuk potiuk closed this Feb 8, 2026
@potiuk potiuk reopened this Feb 8, 2026
@potiuk potiuk force-pushed the run-fab-provider-tests-in-v2-11-test branch 4 times, most recently from 5f4fa9d to 7fd7bf8 Compare February 8, 2026 22:36
Since we are releasing fab provider from v2-11-test we should also
run fab provider tests there.

This chang consists of:

* migrating to FAB 4.5.3 (includes scrypt algorithm fix)
* monkeypatching flask-session so that it works well with new
  flask-sqlalchey
* caching initial$aization of Session class from flask-session and
  AirflowDatabaseSessionInterface so that DB connection is not
  created multiple times during tests
* fixing imports from tests
@potiuk potiuk force-pushed the run-fab-provider-tests-in-v2-11-test branch from 7fd7bf8 to 3957680 Compare February 8, 2026 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch legacy api Whether legacy API changes should be allowed in PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants