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

Automatic file updates make occasional drat workflow failures #22

Open
GegznaV opened this issue Nov 30, 2021 · 1 comment
Open

Automatic file updates make occasional drat workflow failures #22

GegznaV opened this issue Nov 30, 2021 · 1 comment

Comments

@GegznaV
Copy link
Member

GegznaV commented Nov 30, 2021

There is a known issue related to the automatic distribution of files to several repos: the push from pkg-skeleton to other repos triggers GHA workflows on those repos, including drat workflow. The drat workflow tries to push updates to pkg-repo. But when updates from many packages are pushed at the same time, some workflows fail. See details here:

image

A manual restart of the failed drat workflow usually fixes the failure. But I think, we should find a way to disable triggering the drat workflow if the updates come from pkg-skeleton as these are usually setup files that update the infrastructure but do not change the functionality in the package.

Might help:

@GegznaV GegznaV changed the title Automatic file updates make occasional **drat** workflow failures Automatic file updates make occasional drat workflow failures Nov 30, 2021
GegznaV added a commit that referenced this issue Nov 30, 2021
GegznaV added a commit that referenced this issue Dec 1, 2021
@GegznaV GegznaV closed this as completed in 971d9cd Dec 1, 2021
@GegznaV
Copy link
Member Author

GegznaV commented Dec 1, 2021

This issue is not solved yet.

I thought that GitHub actor, who commits to other repos is GitHub bot but it seems to be @cbeleites. The reason, I think, is the fact that DEPLOY_TOKEN that is used to push commits was generated by Claudia.

More investigation is needed to solve this issue.

@GegznaV GegznaV reopened this Dec 1, 2021
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

1 participant