-
Notifications
You must be signed in to change notification settings - Fork 24
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
Infinite Post Job Cleanup w/ Postgres #117
Comments
Hi, thank for reporting an issue, we will check it out very soon |
Hi @vinchg , Here is the documentation to enable debug mode on github action: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/enabling-debug-logging I suggest to re-run your failing job with debug mode enabled (https://docs.github.com/en/actions/managing-workflow-runs/re-running-workflows-and-jobs) Ps: I've updated to documentation (765986d) |
Thanks for the response, I elected to try swapping actions to |
@vinchg thank you for your feedback, I've understood your issue. Log output verbosity is reduced now. |
Description: My docker compose contains postgres, and during post job cleanup, outputs a ridiculous amount of logs and never ends. The documentation seems to describe this behavior as having enabled debug mode, but there is literally no reference on how/when this is done. Any advice would be appreciated. I also wouldn't mind having the option to just not call docker compose down at all.
Action version: 2.0.2 / 2.1.0
Platform:
Repro steps:
And a docker compose with postgres.
The text was updated successfully, but these errors were encountered: