Add better platform diagnostics to see which platform is used by potiuk · Pull Request #57284 · apache/airflow

potiuk · 2025-10-26T08:55:23Z

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types.

Tha name of the workflow is just changed to "Tests"
There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions
The title containing platform is printed at the top of summary
- before the constraints summary.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary.

…used (#57284) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

github-actions · 2025-10-26T09:23:43Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…used (#57284) (#57285) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

gopidesupavan · 2025-10-26T10:42:49Z

Nice :) thanks for updating ..

potiuk · 2025-10-26T08:55:23Z

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types.

Tha name of the workflow is just changed to "Tests"
There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions
The title containing platform is printed at the top of summary
- before the constraints summary.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary.

…used (#57284) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

github-actions · 2025-10-26T09:23:43Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…used (#57284) (#57285) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

gopidesupavan · 2025-10-26T10:42:49Z

Nice :) thanks for updating ..

potiuk · 2025-10-26T08:55:23Z

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types.

Tha name of the workflow is just changed to "Tests"
There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions
The title containing platform is printed at the top of summary
- before the constraints summary.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary.

…used (#57284) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

github-actions · 2025-10-26T09:23:43Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…used (#57284) (#57285) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

gopidesupavan · 2025-10-26T10:42:49Z

Nice :) thanks for updating ..

potiuk · 2025-10-26T08:55:23Z

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types.

Tha name of the workflow is just changed to "Tests"
There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions
The title containing platform is printed at the top of summary
- before the constraints summary.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary.

…used (#57284) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

github-actions · 2025-10-26T09:23:43Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…used (#57284) (#57285) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

gopidesupavan · 2025-10-26T10:42:49Z

Nice :) thanks for updating ..

potiuk · 2025-10-26T08:55:23Z

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types.

Tha name of the workflow is just changed to "Tests"
There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions
The title containing platform is printed at the top of summary
- before the constraints summary.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary.

…used (#57284) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

github-actions · 2025-10-26T09:23:43Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…used (#57284) (#57285) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

gopidesupavan · 2025-10-26T10:42:49Z

Nice :) thanks for updating ..

potiuk · 2025-10-26T08:55:23Z

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types.

Tha name of the workflow is just changed to "Tests"
There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions
The title containing platform is printed at the top of summary
- before the constraints summary.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary.

…used (#57284) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

github-actions · 2025-10-26T09:23:43Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…used (#57284) (#57285) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

gopidesupavan · 2025-10-26T10:42:49Z

Nice :) thanks for updating ..

potiuk · 2025-10-26T08:55:23Z

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types.

Tha name of the workflow is just changed to "Tests"
There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions
The title containing platform is printed at the top of summary
- before the constraints summary.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary.

…used (#57284) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

github-actions · 2025-10-26T09:23:43Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…used (#57284) (#57285) We now have same workflow running for both ARM and AMD and we need a bit better diagnostics printed to distinguish those different run types. * Tha name of the workflow is just changed to "Tests" * There is a job added that should immediately show the platform in the left-sidebar of GitHub Actions * The title containing platform is printed at the top of summary - before the constraints summary. (cherry picked from commit 4219c57) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>

gopidesupavan · 2025-10-26T10:42:49Z

Nice :) thanks for updating ..

potiuk requested review from amoghrajesh, ashb, bugraoz93, eladkal, gopidesupavan, jason810496, jscheffl and kaxil as code owners October 26, 2025 08:55

boring-cyborgBot added area:dev-tools backport-to-v3-1-test labels Oct 26, 2025

eladkal approved these changes Oct 26, 2025
View reviewed changes

potiuk force-pushed the better-platform-diagnostics branch 3 times, most recently from d895dae to 5ae9b8bCompare October 26, 2025 09:08

jscheffl approved these changes Oct 26, 2025
View reviewed changes

potiuk force-pushed the better-platform-diagnostics branch from 5ae9b8b to fd75e8eCompare October 26, 2025 09:12

bugraoz93 approved these changes Oct 26, 2025
View reviewed changes

potiuk force-pushed the better-platform-diagnostics branch from fd75e8e to 8f9b3e2Compare October 26, 2025 09:20

potiuk merged commit 4219c57 into apache:mainOct 26, 2025
26 checks passed

potiuk deleted the better-platform-diagnostics branch October 26, 2025 09:22