Problem with Restyler Job #1113809

[woody-apple]

Hi there-

I'm having a problem with a Restyled Job

• Restyled Job: https://restyled.io/gh/project-chip/repos/connectedhomeip/jobs/1113809
• GitHub PR: Fix ToT failure on avahi project-chip/connectedhomeip#9744

What I expected to happen:
Restyle to complete

What happened instead:
Seemed to timeout multiple times last night

[pbrisbin]

Hey sorry about that, I can indeed see some errors for your repository, with a small cluster from last night:

However, only 2 of these in the past week were errors talking to GitHub (the example you gave). Those errors aren't anything we can help with, unfortunately. GitHub is responding 502 which indicates their servers are unable to serve our request for some reason -- basically an outage on their part.

The "system" errors could be a few things, but I found one, which is:

 ! [remote rejected]     restyled/pull-9744 -> restyled/pull-9744 (refusing to allow a GitHub App to create or update workflow `.github/workflows/examples-esp32.yaml` without `workflows` permission)

This is another unfortunate situation we can't address, but you can read more details here.

Are the GitHub-502 and push-rejected errors the only ones you are seeing, or is there something else I can look into for you?

[woody-apple]

(Sorry for the delay, my notifications seem to be not working) Thanks for looking at this! The 502 ones were the ones we were hitting. Is there an easy way for me to re-kick a job, and/or have an auto retry? Unfortunately when there’s an issue, there’s no easy way for a developer to re-kick the restyle job. (Short of force push)

[pbrisbin]

We used to have a retry feature, but it was a bit of complexity and infrequently used. So as of right now, force-pushing an amend or pushing an empty commit is the only way to re-trigger Restyled. I personally like to git commit --allow-empty because they will be automatically removed if you use the Rebase strategy to merge on GitHub.

I will open a feature request for bringing back Retry and put it in the Backlog.

[pbrisbin]

#162