potiuk commented on PR #63103: URL: https://github.com/apache/airflow/pull/63103#issuecomment-4323610438
@diligejy This PR has been converted to **draft** because it does not yet meet our [Pull Request quality criteria](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-quality-criteria). **Issues found:** - :x: **Failing CI checks**: 15 `Basic tests / Shared *` tests are failing past the 96h grace window — `Basic tests / Shared listeners tests`, `Basic tests / Shared timezones tests`, `Basic tests / Shared secrets_masker tests`, `Basic tests / Shared configuration tests`, `Basic tests / Shared logging tests` (+10 more). The pattern suggests a foundational change is breaking shared test suites. Please investigate and rebase onto the latest `main` first to rule out base-branch drift. **What to do next:** - Rebase onto the latest `main` (`git fetch upstream main && git rebase upstream/main`). - Investigate the root cause of the shared-test failures. - Run `breeze testing core-tests` locally on a few of the failing tests to reproduce. - Mark the PR as "Ready for review" when CI is green. Converting a PR to draft is **not** a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the [Airflow Slack](https://s.apache.org/airflow-slack). --- _Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this [two-stage triage process](https://github.com/apache/airflow/blob/main/contributing-docs/25_maintainer_pr_triage.md#why-the-first-pass-is-automated) so that our maintainers' limited time is spent where it matters most: the conversation with you._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
