When building on a Windows slave, which is started via SSH and Cygwin, git fetch fails more often than not with:

Started by upstream project "MATE" build number 109
Building remotely on build-win
Checkout:build-win / <http://hudson.mv.cariden.com/job/MATE/./label=build-win/ws/> - hudson.remoting.Channel@1268d3c:build-win
Using strategy: Default
Last Built Revision: Revision 381957510fd7a4ccb9f563ce7b5cbc47301c4e38 (origin/master)
Checkout:build-win / C:\var\hudson\workspace\MATE\label\build-win - hudson.remoting.LocalChannel@156dbdd
GitAPI created
Fetching changes from the remote Git repository
Fetching upstream changes from ssh://cariden@git.mv.cariden.com/var/git/mate.git
[build-win] $ git fetch -t ssh://cariden@git.mv.cariden.com/var/git/mate.git +refs/heads/:refs/remotes/origin/
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
ERROR: Could not fetch from any repository
FATAL: Could not fetch from any repository

Our system is set up to build on four other slaves (Mac OSX, Linux, Solaris x86, and Solaris Sparc), and none of them show the same problem.

If I SSH into the Windows machine as user "cariden", and then SSH into git.mv.cariden.com, "git" is in the PATH and everything is fine. It must have something to do with the way Hudson/Git is trying to execute that command, but from the log I can't really tell much.

The weird part is that sometimes it works. It used to work every time, but failures are happening more and more often.