-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Tests (stable) error #9
Comments
Hmm, this is working OK elsewhere. It looks like this has already failed 4 days in a row though. |
I recommend opening an issue in https://github.com/gautamkrishnar/keepalive-workflow - it's sure not clear to me what's going on. Also, manually trigger the tests if you can. |
I'm getting the same error on ddev-vscode-devcontainer also started but after making a commit, the scheduled tests started passing. |
I see things like ddev-drupal9-solr continuing as always. I do wonder if it's something changed about the power of the default github token or the configuration of the project. |
@tyler36 I changed your role on ddev-drupal9-solr to admin so you can have full privs to try to compare it to the projects that are failing, thanks! And of course compare the current version of https://github.com/gautamkrishnar/keepalive-workflow |
Perhaps Github changed something to prevent actions like keepalive from working around their cutoff. |
That may be. But I would think it would be affecting everything by now, and I haven't seen it on the ones I maintain. Good reason for an issue in https://github.com/gautamkrishnar/keepalive-workflow |
issue #9: fixes the keepalive permissions.
Thanks for paying attention to this, and thanks so much for maintaining this add-on. But I don't think we know it's solved until a commit has happened. |
Thank you @rfay for your supervision! Now the scheduled test action has successfully rerun, is it a sign that it is fixed, or not? |
Thanks so much for maintaining this! The problem here is that the job of this is to push a commit, and that's what failed (it wasn't the action/workflow itself). But it only does it after |
The job tests (stable) fail with the following error:
The text was updated successfully, but these errors were encountered: