rsync icon indicating copy to clipboard operation
rsync copied to clipboard
verified publisher icon WayneD

Notifications from github about a failed macOS test run

Open mruprich opened this issue 1 year ago • 4 comments

Hi, right after I filed https://github.com/RsyncProject/rsync/pull/716 I started receiving notifications about a failed test on macOS workflow:

Image

I have no idea why I am getting this - all tests are green in the PR and there is no macOS run anywhere. I get it once a day, it is getting a bit annoying. Also I did not find any way to disable it or turn off this particular notification. If this looks more like a bug for github, I am happy to bring this up with the support. But it seems to me that there is some sort of a hidden workflow somewhere that generates these. Any help with this is appreciated.

Regards, Michal Ruprich

mruprich avatar Jan 23 '25 09:01 mruprich

the run is from https://github.com/mruprich/rsync

example: https://github.com/mruprich/rsync/actions/runs/12828280387/job/35771980400

If you are unsure what broke and don't need a copy of the repo - just delete your fork and you should be good to go.

sudhackar avatar Jan 23 '25 13:01 sudhackar

Hi, thanks, I understand that this is coming from my fork, but I created this fork years ago because I occasionally contribute to rsync. I never enabled any testing pipelines on the fork nor have I ever seen any such notifications until the moment when I posted the above PR. I am trying to get to the bottom of the problem here (why is the pipeline there, how do I disable it). Deleting the fork is the last resort.

mruprich avatar Jan 23 '25 14:01 mruprich

Oh sorry if that sounded rude. The Github Action is defined here - https://github.com/RsyncProject/rsync/blob/master/.github/workflows/macos-build.yml

https://github.com/RsyncProject/rsync/actions/workflows/macos-build.yml says this workflow was disabled manually The last run was 3 months ago and last successful run was 9 months ago. So maybe you can disable it in your fork as well.

sorry again.

sudhackar avatar Jan 23 '25 14:01 sudhackar

Nono, it did not sound rude, I didn't mean it that way, sorry. But I would rather solve it than just delete the fork.

I have a correction to make though, it was not triggerred with the PR but rather with me syncing my fork with the master. The workflow points to the last commit in master - 23d9ead5af0249babf241c5917ea2b22c2754bcb

I see that the macos yaml file has not been updated in a while and no macOS run is in the recent PR so I assumed that it is not being used anymore?

I will take a look in the fork and see if I can find a way to disable it there.

mruprich avatar Jan 23 '25 14:01 mruprich