Skip to content

Pin the real selective-checks auto-approve test to main - #75682

Merged
shahar1 merged 1 commit into
apache:mainfrom
potiuk:pin-auto-approve-test-to-main
Oct 26, 2026
Merged

shahar1 merged 1 commit into
apache:mainfrom
potiuk:pin-auto-approve-test-to-main

Conversation

@potiuk

@potiuk potiuk commented Oct 26, 2026

Copy link
Copy Markdown
Member

test_decide_approval_with_real_selective_checks decides approval for a PR targeting main, but built SelectiveChecks with the checkout's default branch. It passes on main today, but on a release branch selective checks skip provider tests, so the large provider change is estimated cheap and approved, failing the test. That already happened when backporting the auto-approval changes to v3-4-test (#75680). The test now pins default_branch="main", as build_selective_checks already does in production.

Checks run locally: dev/breeze/tests/test_workflow_run_approval.py (117 passed).


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Opus 5

Generated-by: Claude Opus 5 following the guidelines

🤖 Generated with Claude Code

The test decides approval for a PR targeting main, but built SelectiveChecks
with the checkout's default branch. On a release branch that skips provider
tests, so the large provider change was estimated cheap and approved.

Generated-by: Claude Opus 5
@shahar1
shahar1 merged commit 36038d7 into apache:main Oct 26, 2026
56 of 57 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Backport failed to create: v3-4-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
❌ v3-4-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 36038d7 v3-4-test

This should apply the commit to the v3-4-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants