Repository navigation
Stop running OpenLineage e2e compat tests when full tests are derived - #75262
Merged
potiuk merged 1 commit intoOct 28, 2026
Merged
Conversation
FrankYang0529
marked this pull request as ready for review
October 23, 2026 02:29
FrankYang0529
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl,
potiuk and
vatsrahul1001
as code owners
October 23, 2026 02:29
FrankYang0529
force-pushed
the
fix-openlineage-compat-derived-full-tests
branch
from
October 23, 2026 09:30
81674f2 to
ce777c4
Compare
Signed-off-by: PoAn Yang <payang@apache.org>
FrankYang0529
force-pushed
the
fix-openlineage-compat-derived-full-tests
branch
from
October 27, 2026 02:06
ce777c4 to
df73418
Compare
potiuk
approved these changes
Oct 28, 2026
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Oct 28, 2026
… are derived (apache#75262) (cherry picked from commit e31f52e) Co-authored-by: PoAn Yang <payang@apache.org> Signed-off-by: PoAn Yang <payang@apache.org>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Oct 28, 2026
… are derived (apache#75262) (cherry picked from commit e31f52e) Co-authored-by: PoAn Yang <payang@apache.org> Signed-off-by: PoAn Yang <payang@apache.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
run_ui_e2e_tests. Run OpenLineage e2e compat tests when the compat setup changes #69866 kept a comment saying so, but maderun_openlineage_e2e_compat_testsfall back to_should_be_run(...), which returnsTruewheneverfull_tests_neededisTrue. So selective checks turn the matrix on (five jobs onmaintoday) in every PR run where they derive full tests.ci-amd.ymlPR runs that ran the compat jobs did so only because full tests were derived. In those 29 runs, the compat matrix ran 145 jobs for 1,008 runner-minutes, about 1% of the runner-minutes used byci-amd.ymlPR runs that day.The 29 runs from 2026-10-15
The table lists every
ci-amd.ymlpull_request run created on 2026-10-15 (UTC) that ran the OpenLineage e2e compat jobs. Minutes arecompleted_at - started_at, summed over the "OpenLineage e2e compat" jobs and counting every attempt. All 235 PR runs that day used 100,144 runner-minutes.pyproject.tomlpyproject.tomlHow
run_openlineage_e2e_compat_testskeeps the canary and label checks. After those checks, it only matches the changed files againstOPENLINEAGE_E2E_COMPAT_FILES..github/workflows/openlineage-e2e-compat-tests.ymltoOPENLINEAGE_E2E_COMPAT_FILES.airflow-e2e-tests/docker/openlineage-compat-db.yml, which Core: Make psycopg (v3) the default synchronous Postgres driver #69469 added after Run OpenLineage e2e compat tests when the compat setup changes #69866.Was generative AI tooling used to co-author this PR?