Fix E2E Flaky Tests Report failing with gh api 404#65120
Merged
potiuk merged 1 commit intoapache:mainfrom Apr 13, 2026
Merged
Conversation
scripts/ci/analyze_e2e_flaky_tests.py builds 'gh api <endpoint> -f key=val ...' to list workflow runs. The gh CLI defaults to POST whenever -f parameters are present, so the workflow runs endpoint returned 'Not Found (HTTP 404)' and the script wrote no output file, causing the downstream slack-github-action step to crash with ENOENT on slack-message.json. Force --method GET in the gh_api helper and add a regression test.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-2-test
vatsrahul1001
approved these changes
Apr 13, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Apr 13, 2026
scripts/ci/analyze_e2e_flaky_tests.py builds 'gh api <endpoint> -f key=val ...' to list workflow runs. The gh CLI defaults to POST whenever -f parameters are present, so the workflow runs endpoint returned 'Not Found (HTTP 404)' and the script wrote no output file, causing the downstream slack-github-action step to crash with ENOENT on slack-message.json. Force --method GET in the gh_api helper and add a regression test. (cherry picked from commit 7ae29fb) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Apr 13, 2026
…e#65120) scripts/ci/analyze_e2e_flaky_tests.py builds 'gh api <endpoint> -f key=val ...' to list workflow runs. The gh CLI defaults to POST whenever -f parameters are present, so the workflow runs endpoint returned 'Not Found (HTTP 404)' and the script wrote no output file, causing the downstream slack-github-action step to crash with ENOENT on slack-message.json. Force --method GET in the gh_api helper and add a regression test. (cherry picked from commit 7ae29fb) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
Apr 13, 2026
… (#65157) scripts/ci/analyze_e2e_flaky_tests.py builds 'gh api <endpoint> -f key=val ...' to list workflow runs. The gh CLI defaults to POST whenever -f parameters are present, so the workflow runs endpoint returned 'Not Found (HTTP 404)' and the script wrote no output file, causing the downstream slack-github-action step to crash with ENOENT on slack-message.json. Force --method GET in the gh_api helper and add a regression test. (cherry picked from commit 7ae29fb) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
dandanseo123
pushed a commit
to dandanseo123/airflow
that referenced
this pull request
Apr 13, 2026
scripts/ci/analyze_e2e_flaky_tests.py builds 'gh api <endpoint> -f key=val ...' to list workflow runs. The gh CLI defaults to POST whenever -f parameters are present, so the workflow runs endpoint returned 'Not Found (HTTP 404)' and the script wrote no output file, causing the downstream slack-github-action step to crash with ENOENT on slack-message.json. Force --method GET in the gh_api helper and add a regression test.
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
2 participants
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.
Summary
The nightly E2E Flaky Tests Report workflow has been failing — see run 24320225760 / job 71004915159. The "Analyze E2E test results" step prints:
Root cause
The `gh` CLI defaults to POST whenever `-f`/`-F` parameters are present. The workflow runs list endpoint returns 404 on POST, which is exactly the error in the log.
Fix
Verified locally that the broken call returns 404 and the fixed call returns the expected payload.
Test plan
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.6) following the guidelines