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

Head commit for run:
ff140cd0b4a048287ed0c069b8de9659aebf6c34 / Jason(Zhe-You) Liu 
<[email protected]>
Support inline ignore marker for check_core_imports_in_sdk hook (#65358)

* Support # nocheck: core-imports inline marker for check_core_imports_in_sdk 
hook

* Address review comment

* refactor: streamline import checks and update nocheck markers to noqa

* refactor: streamline import checks and update nocheck markers to noqa

* Restrict noqa code parsing to the leading comma-separated list

A comment like `# noqa: F401 - see SDK002 docs` no longer
accidentally suppresses SDK002 — codes mentioned in the trailing
explanation are ignored.

* Add positive test cases for noqa codes with trailing explanation

Cover `# noqa: F401, SDK002 - needed for compat` (suppresses SDK002
because it's part of the leading code list) and the symmetric case
for the SDK001 hook.

* Tighten noqa code parsing and detect bare-module attribute imports

- Anchor `_NOQA_CODE_RE` with a word boundary so prefixes like
  `SDK002x` no longer suppress `SDK002`.
- Extend the ImportFrom check to also test `<module>.<name>` so that
  `from airflow import settings` is reported as a core import. Mixed
  imports like `from airflow import sdk, settings` report only the
  offending names.

* Print noqa suppression hint when an import violation is reported

After listing offending imports, ``report_import_violations`` now
echoes the ``# noqa: <code>`` escape hatch so users know the exact
marker to add for an intentional import without having to dig into
the hook source.

* fixup: Add SDK002 ignore in task-sdk

* Rename check_sdk_imports to check_sdk_imports_in_core

Mirrors the naming of the sibling check_core_imports_in_sdk hook so the
direction of each guard (what's checked in where) is obvious from the
filename.

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

With regards,
GitHub Actions via GitBox


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

Reply via email to