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

Migration logs some errors during accept #156

Open
areebrtc opened this issue May 31, 2019 · 2 comments
Open

Migration logs some errors during accept #156

areebrtc opened this issue May 31, 2019 · 2 comments
Labels

Comments

@areebrtc
Copy link

My migration takes about 3-4 days to run, and it is still running. However, I am seeing some errors regarding 'accept'. The following form of logging is reported as below: -

To /data/STREAM/myGitRepo.git
a1c4641..04045ad HEAD -> CC-6.1.0.2-Stream_branchpoint
Problem running 'accept':

Successfully loaded items into the sandbox.

On branch _branchpoint

nothing to commit, working directory clean

20:17:14 - No changes for commiting in git detected, going to reload the workspace

It is something which could hinder migration process and result in less accurate migration having missing file and directories after migration is completed.

Please comment on this.

@WtfJoke
Copy link
Member

WtfJoke commented May 31, 2019

Do you have more logs of Problem running 'accept'?
Usually its written there what happen, unless the workspace contains too much conflicts

@areebrtc
Copy link
Author

Yes I saw log that only mentions Problem running 'accept' and nothing else is there which point to some reason of failure and it is happening frequently. Also, I saw that there were conflicts in 4 files when I stopped migration and manually ran
"scm show conflicts"

Can you suggest how to proceed from here? Do we need to resolve conflicts manually every-time it happens or enabling auto-conflict resolution can solve the purpose?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants