The GitHub Actions job "Tests" on airflow.git/main has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
fcb2eb64704b66244975ec84d585f675aba24464 / Dheeraj Turaga 
<[email protected]>
Introduce EdgeDBManager: Independent Provider Specific Database Schema 
Management (#61155)

* Add EdgeDBManager for provider-specific database migrations

  Implement EdgeDBManager to integrate Edge3 provider with Airflow's
  external database manager system, enabling independent schema version
  control for Edge3 tables separate from core Airflow migrations.

  This enables Edge3 provider to manage its database schema evolution
  independently from core Airflow, allowing for provider-specific version
  control and migration management. The infrastructure is ready for use
  once initial migration files are generated and the legacy _check_db_schema()
  approach in EdgeExecutor.start() is removed.

* Add table creation support to EdgeDBManager via Alembic migration

  Wire up the full initdb/create_db_from_orm lifecycle in EdgeDBManager
  so table creation is handled through proper Alembic migrations instead
  of ad-hoc metadata.create_all() in EdgeExecutor.start().

  - Create initial Alembic migration (0001_3_0_0) for edge_worker,
    edge_job, and edge_logs tables with if_not_exists=True
  - Replace _check_db_schema() + metadata.create_all() in
    EdgeExecutor.start() with EdgeDBManager.initdb()
  - Remove legacy _check_db_schema() (Airflow 2.x workaround)
  - Add edge3 support to check_revision_heads_map.py pre-commit script
  - Add check-revision-heads-map-edge3 pre-commit hook
  - Rename migrations README to README.md
  - Add tests for create_db_from_orm, initdb, and revision_heads_map

* Add missing test file for edge3 migrations env module

  The test_project_structure check requires every provider source module
  to have a corresponding test file. Add test_env.py for the migrations
  env.py module with tests for version table name and metadata contents.

* Skip DB lock acquisition when edge3 migrations are already current

  Add a fast-path check_migration() call before acquiring the global
  advisory lock in EdgeExecutor.start(). This avoids unnecessary lock
  contention when multiple API server instances start simultaneously
  and the database is already at the target migration state.

* Add session-scoped fixture to create edge3 tables for tests

  Since edge3 tables are managed via separate _edge_metadata (removed
  from Base.metadata), the test framework's initdb no longer creates
  them. Add a session-scoped autouse fixture in conftest.py that creates
  the tables once for all edge3 tests.

* Fix edge3 test failures

  - Guard _create_edge_tables conftest fixture against settings.engine
    being None when non-DB tests (CLI) run in the same session
  - Patch _check_valid_db_connection in test_list_edge_workers since
    the test env sql_alchemy_conn equals the default value

* Jens suggestions

Report URL: https://github.com/apache/airflow/actions/runs/22172931960

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to