Skip to content

feat: inspect docker compose failure on self-hosted e2e action #3817

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 19, 2025

Conversation

aldy505
Copy link
Collaborator

@aldy505 aldy505 commented Jul 18, 2025

It's hard to debug docker compose failure on other repositories since they can't see the docker compose ps and docker compose logs. One problem occurred here: getsentry/relay#4940

This PR aims to provide both commands if failure happens.

Copy link

codecov bot commented Jul 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.45%. Comparing base (0f2748e) to head (8373380).
Report is 1 commits behind head on master.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3817   +/-   ##
=======================================
  Coverage   99.45%   99.45%           
=======================================
  Files           3        3           
  Lines         183      183           
=======================================
  Hits          182      182           
  Misses          1        1           

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

@BYK BYK merged commit 9fbd722 into master Jul 19, 2025
13 checks passed
@BYK BYK deleted the aldy505/feat/action-inspect-failure branch July 19, 2025 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants