Failed to submit 2 changes due to the following problems:
Change 339157: internal error: change not processed by merge strategy
Change 339158: internal error: change not processed by merge strategy
Details:
1. I have set the Submit Type as "Rebase if Necessary" in the repo.
2. I have rebased all the patchsets.
Could you please help me to resolve this issue.
Regards,
Renuka
Hi Team,I have a problem in submitting the Changes in my Gerrit instance. The Gerrit version installed is 2.13.2. When I am trying to submit the Change including parents, I am getting the below error. But as checked, there are no errors in the error log. I have also tried to "Submit" the parent change alone i.e "339157". But getting the same error. Attaching the error screenshots.Failed to submit 2 changes due to the following problems:
Change 339157: internal error: change not processed by merge strategy
Change 339158: internal error: change not processed by merge strategy
Details:
1. I have set the Submit Type as "Rebase if Necessary" in the repo.
2. I have rebased all the patchsets.
Could you please help me to resolve this issue.
Regards,
Renuka
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
error: fatal: Failed to submit 6 changes due to the following problems:
Change 3276126: internal error: change not processed by merge strategy
Change 3287577: internal error: change not processed by merge strategy
Change 3290098: Project policy requires all submissions to be a fast-forward. Please rebase the change locally and upload again for review.
Regards,Hi Folks,We are still facing this issue in version 2.16.22. All the below mentioned projects are under FF Merging strategy . we are not able to get much logs in the error_log to check more on this issues.