6
Vote

git tf checkin "0%, examining repository"

description

Hello,

I am working with a rather large repository. It has close to 11,000 files. I pulled the code from git hub, and was able to check it in using git tf checkin. That was a couple days ago. Now there are some changes on git that I want to pull into TFS. I was able to pull the changes down and merge them in to my local repo. There were less than a dozen files that changed. Now, when I run git tf checkin to check the changes into TFS I get the following message

Checkin in to $/<TFS path>: 0%, examining repository

It just sits there and nothing else happens. It never gets past 0%. I thought maybe it would take a while so I just let it sit. However, it has been sitting at that point for over three hours. I tried yesterday too, and let it sit for over an hour before I killed it. Is this thing stuck, or is it just taking a really long time? Is there something to do to speed it up?

Thanks for your help!

file attachments

comments

dschopenp wrote Nov 1, 2012 at 7:19 PM

Also, I noticed that a Java process was at 30% cpu utilization. When I killed the command this process went away. So, the command must have been doing something, but not sure if it was actually making progress or was stuck.

dschopenp wrote Nov 1, 2012 at 7:48 PM

I was reading through some additional documentation, and I tried git tf checking --deep and the changes checked in within a couple minutes. So it must be something with the default option.

youhanaNaseim wrote Nov 7, 2012 at 2:52 PM

Hello,

Thanks for reporting the issue. Can you please share the logs here : %LOCALAPPDATA%\Microsoft\Team Foundation\4.0\Logs

Thanks,
Youhana

Rupe wrote Nov 15, 2012 at 5:20 PM

I've waited for over a 30 minutes with it saying "0%, examining repository"

Rupe wrote Nov 15, 2012 at 5:23 PM

Here is the soap log

I'm using the latest 2.0 version from Chocolatey: http://chocolatey.org/packages/Git-TF/2.0.0.20121030

Rupe wrote Nov 15, 2012 at 5:45 PM

I was able to get passed this by performing a small inconsequential check in within TFS. I pulled the change into my Git repo and then tried a git tf checkin again and it worked.

Rupe wrote Nov 20, 2012 at 3:27 AM

Making a change in TFS directly, checking in the change, performing a git tf pull and then a git tf checkin, has so far been a very reliable fix

youhanaNaseim wrote Dec 26, 2012 at 4:23 PM

Hello, sorry for the late reply.

What is happening is that git tf is computing the difference between HEAD and the last commit that was integrated with tfs. When checking in shallow mode (the default) if git and tfs have not been synced for a long time, the difference computation will have higher complexity than checking in one commit at a time using the (--deep) mode, that is why (-deep) finished in a couple of minutes.

Thanks for reporting the performance issue. Can you provide us more details about your repo, such as size, number of files, number of files that changed that will be checked in tfs ?

Thanks,
Youhana

youhanaNaseim wrote Dec 26, 2012 at 4:25 PM

Thank you very much Rupe for providing the logs. We will look into enhancing the performance here.

Ncage1974 wrote Sep 4, 2014 at 6:42 PM

I'm having this same problem. Its been sitting there for over an hour. Before i had this issue i synced to TFS like 10 minutes before (i had the latest code from TFS). So the issue your describing of not having synced with TFS for awhile was not my issue. I then had 3 small web.config file changes i needed to make. When trying to sync them to TFS is when i got the issue. My previous commit (10 minutes prior) was much much larger.

Ncage1974 wrote Sep 4, 2014 at 6:44 PM

I'm uploading my logs....

Ncage1974 wrote Sep 4, 2014 at 7:59 PM

to fix i had to have someone make a very small change in tfs. I then a pull and then i was able to commit the files. I tried the previous recommendation of doing a --deep option but i just ended up getting an error saying i couldn't lock the files...

craighess wrote May 12, 2016 at 9:20 PM

Also experiencing the same thing. I was able to work around it in the same manor by checking a minor change into TFS, pulling it down with git-tf and then I was able to check in as normal.

I suppose the git-tf project is officially dead since there hasn't been an update since Thu Dec 19, 2013.