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

😿 Failed to sync the upstream PRs: #103, #105 #422

Closed
magic-mirror-bot bot opened this issue Feb 13, 2023 · 1 comment · Fixed by #423
Closed

😿 Failed to sync the upstream PRs: #103, #105 #422

magic-mirror-bot bot opened this issue Feb 13, 2023 · 1 comment · Fixed by #423

Comments

@magic-mirror-bot
Copy link

🪞 Magic Mirror 🪞 failed to sync the following upstream pull-requests because one or more patches couldn't cleanly apply:

Syncing is paused for the branch main on stolostron/config-policy-controller until the issue is manually resolved and this issue is closed.

Commands to recreate the issue:

git cherry-pick -x 167fb5753c7a935909e200b1f6bae29078ed2098~1..167fb5753c7a935909e200b1f6bae29078ed2098 --allow-empty --keep-redundant-commits
git cherry-pick -x 8203f5fb9e5fbd72b85852d54f7bd91331c298ce~1..8203f5fb9e5fbd72b85852d54f7bd91331c298ce --allow-empty --keep-redundant-commits

sad Yoda

@dhaiducek
Copy link
Contributor

@JustinKuli The failure here looks like it's because it tried to handle two PRs and maybe didn't exactly work?

2023-02-13T21:45:40.687Z  error  	Failed to apply the patches on the "main" branch on stolostron/config-policy-controller from the following PRs from  open-cluster-management-io/config-policy-controller 103, 105: Error: ENOTEMPTY: directory not empty, rmdir '/tmp/tmp-17-DaeJl1n0NEl0/.git'
2023-02-13T21:45:41.431Z  info  	Created the GitHub issue #422 on stolostron/config-policy-controller to notify of the failure

@mprahl mprahl reopened this Feb 16, 2023
@mprahl mprahl closed this as completed Feb 16, 2023
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

Successfully merging a pull request may close this issue.

2 participants