Skip to content

feat(test-cli): always print full pytest command in ci & add to summary#2719

Open
danceratopz wants to merge 3 commits intoethereum:forks/amsterdamfrom
danceratopz:always-print-full-pytest-command-in-ci
Open

feat(test-cli): always print full pytest command in ci & add to summary#2719
danceratopz wants to merge 3 commits intoethereum:forks/amsterdamfrom
danceratopz:always-print-full-pytest-command-in-ci

Conversation

@danceratopz
Copy link
Copy Markdown
Member

🗒️ Description

If pytest commands get -v they print the full pytest invocation (with ini file path, etc) to the console. This PR additionally enables this if the command is running in CI and also adds this command to the job's summary.

🔗 Related Issues or PRs

N/A.

✅ Checklist

  • All: Ran fast static checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:
    just static
  • All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
  • All: Considered updating the online docs in the ./docs/ directory.
  • All: Set appropriate labels for the changes (only maintainers can apply labels).

Cute Animal Picture

🐭

@danceratopz danceratopz added C-feat Category: an improvement or new feature A-test-cli Area: execution_testing.cli labels Apr 19, 2026
Check the `CI` environment variable so that `fill` (and other
pytest-based commands) print the resolved `pytest ...` command
line in GitHub Actions without requiring `-v`.
Add a "Debugging CI Failures" subsection to `docs/dev/test_actions_locally.md`
pointing readers at the `Executing: pytest ...` line printed when `CI` is
set, so failing Github Actions jobs can be reproduced locally without
`gh act`.
When `$GITHUB_STEP_SUMMARY` is set, `PytestRunner` now also appends the
resolved `pytest ...` invocation to the step summary as a fenced code
block, so it can be copied from the Actions "Summary" panel of a failing
run instead of scrolling through the log. Outside Github Actions the
env var is unset and behavior is unchanged.
@danceratopz danceratopz force-pushed the always-print-full-pytest-command-in-ci branch from f0b62e1 to 286e5e7 Compare April 19, 2026 23:43
@danceratopz danceratopz marked this pull request as ready for review April 20, 2026 05:50
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.26%. Comparing base (e8f01a6) to head (286e5e7).
⚠️ Report is 1 commits behind head on forks/amsterdam.

Additional details and impacted files
@@                 Coverage Diff                 @@
##           forks/amsterdam    #2719      +/-   ##
===================================================
+ Coverage            84.72%   86.26%   +1.53%     
===================================================
  Files                  524      599      +75     
  Lines                31117    37038    +5921     
  Branches              3036     3795     +759     
===================================================
+ Hits                 26365    31949    +5584     
- Misses                4181     4525     +344     
+ Partials               571      564       -7     
Flag Coverage Δ
unittests 86.26% <ø> (+1.53%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-test-cli Area: execution_testing.cli C-feat Category: an improvement or new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant