-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
process exit error #69
Comments
Same here, our GH Action has been in place for months. It started failing for us this morning with no changes. This has happened to us one other time and the issue resolved itself after a few hours. I am not able to identify why it's failing. |
To fix this I changed: |
It seems the fix does not work anymore ... seems like the issue is also in specific versions v3 + v4 now |
If you re-run with debug logs, does it say anything about ghcr.io? There was an outage yesterday, but it resolved itself within minutes. |
Just re-run without debug logs and still the same error. How do I enable debug logs? |
Thanks! No, it does not say anything about ghcr. |
hmmmmmpf let me do some investigations. I'm currently pushing some commits that are tested with this action... will report back here. |
Should be related to the latest commit from yesterday: 69225c0 |
For anyone who’s interested. This warning seems to be causing this issue:
It seems that having this warning printed causes the action to be considered as faulty. The workaround is to use:
assuming you’re using only one test suffix. If you’re using more, then there is no way of solving it afaik, as the default is set to:
If I have time I may be able to provide a fix for it here via PR. This has been described here as well: |
Throws a warning
But at least the phpunit step does not error out for me anymore. Also working again on latest @v4 for me. Thanks! |
@mschielmann its:
|
My yml is as follows:
Getting the following error since today:
Previously everything was running fine and I didn't touch anything regarding github actions, the .yml file or phpunit configuration or tests.
Any ideas?
The text was updated successfully, but these errors were encountered: