Skip to content
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

Closed
robertoperuzzo opened this issue Jun 11, 2023 · 11 comments
Closed

Tests (stable) error #9

robertoperuzzo opened this issue Jun 11, 2023 · 11 comments

Comments

@robertoperuzzo
Copy link
Collaborator

The job tests (stable) fail with the following error:

Run gautamkrishnar/keepalive-workflow@v1
  with:
    gh_token: ***
    commit_message: Automated commit by Keepalive Workflow to keep the repository active
    committer_username: gkr-bot
    committer_email: gkr-bot@tuta.io
    time_elapsed: 50
    auto_push: true
  env:
    NIGHTLY_DDEV_PR_URL: https://nightly.link/ddev/ddev/actions/runs/1720215802/ddev-linux-amd64.zip
    DDEV_GITHUB_TOKEN: ***
    HOMEBREW_NO_INSTALL_FROM_API: 1
Error: {"command":"git push origin HEAD","exitCode":128,"outputData":"","errorData":"remote: Permission to robertoperuzzo/ddev-sqlsrv.git denied to github-actions[bot].\nfatal: unable to access 'https://github.com/robertoperuzzo/ddev-sqlsrv.git/': The requested URL returned error: 403\n"}
@rfay
Copy link
Member

rfay commented Jun 11, 2023

Hmm, this is working OK elsewhere. It looks like this has already failed 4 days in a row though.

@rfay
Copy link
Member

rfay commented Jun 11, 2023

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.

@tyler36
Copy link
Contributor

tyler36 commented Jun 12, 2023

I'm getting the same error on

ddev-vscode-devcontainer also started but after making a commit, the scheduled tests started passing.

@rfay
Copy link
Member

rfay commented Jun 12, 2023

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.

@rfay
Copy link
Member

rfay commented Jun 12, 2023

@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

@tyler36
Copy link
Contributor

tyler36 commented Jun 12, 2023

Perhaps Github changed something to prevent actions like keepalive from working around their cutoff.

@rfay
Copy link
Member

rfay commented Jun 12, 2023

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

robertoperuzzo added a commit that referenced this issue Jun 12, 2023
issue #9: fixes the keepalive permissions.
@robertoperuzzo
Copy link
Collaborator Author

robertoperuzzo commented Jun 13, 2023

Thank you @tyler36 I did the same update as you here and the keepalive is back to work.

I close this issue.

@rfay
Copy link
Member

rfay commented Jun 13, 2023

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.

@robertoperuzzo
Copy link
Collaborator Author

Thank you @rfay for your supervision!

Now the scheduled test action has successfully rerun, is it a sign that it is fixed, or not?
Probably I miss something ;)

@rfay
Copy link
Member

rfay commented Jun 13, 2023

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 time_elapsed days without a commit. you just did a commit. So it's a given that for the next 50 days this will succeed (that's the default time_elapsed in there, see https://github.com/gautamkrishnar/keepalive-workflow#for-github-action). If you want to prove that it's going to work now sooner, you can temporarily change the time_elapsed to 1 for example and wait a couple of days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants