[v3-2-test] Skip test_schedule_tis_start_trigger pending #55068 backport decision#66309
Merged
potiuk merged 1 commit intoapache:v3-2-testfrom May 3, 2026
Merged
Conversation
…backport decision The `start_from_trigger` deferred-at-schedule path is commented out on v3-2-test (disabled in 91e1029 as a TODO) and was only re-enabled on main by apache#55068, which landed one day after the v3-2 branch was cut. The test asserts the feature works and fails on v3-2-test CI. Skip the test on the 3.2 line and link the tracking issue from both the test skip-reason and the disabled production-code site so the follow-up isn't lost. Decision (backport apache#55068 or formally drop the feature on 3.2) is tracked in apache#66307.
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
1 participant
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.
The
test_schedule_tis_start_triggertest fails onv3-2-testbecausethe
start_from_triggerdeferred-at-schedule code path inDagRun.schedule_tisis commented out as a TODO on this branch.That path was re-enabled on
mainby #55068 (merged 2026-03-25), oneday after
v3-2-testwas cut. The PR is a 19-file feature changethat's too large to backport blindly into a release branch, so the
right call here is the conservative one: skip the test, link a
tracking issue at both the skip-reason and the disabled production-code
site, and leave the underlying decision (option 1: backport #55068,
option 2: formally drop
start_from_triggeron 3.2) to the issue.closes: nothing yet — see #66307 for the open decision
Failing CI run that surfaced this:
https://github.com/apache/airflow/actions/runs/25270258994/job/74097048671
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.7) following the guidelines