Remco;7738 wrote:Hi, thanks for sharing this issue.
NCrunch pipes data over a standard TCP connection. It has a built-in timeout period using keepalive packets to try and keep the connection open when no work is being performed. The connectivity code has been pretty thoroughly tested with much larger uploads .. so why the connection is being broken in this case is somewhat of a mystery to me.
Do you have any files in your solution that are unusually large? (for example, over 100MB).
Something that may help you is that the NCrunch grid node has the ability to index and re-use files that already exist under its snapshot directory at the time the node is first initialised. Once the files are upload, the engine won't upload them again. If you can copy up the solution files to Azure manually (through FTP or some other means) then place them alongside the other files that the grid node has already uploaded into the snapshot, the node should start making use of these files the next time it is initialised. This will allow you to get past the copy step and start using the node.
Hmm the source tree is about 3.9gb including components and blobs. No file is above 50mb though.
Hah just fixed it - had an excel data file open with changes. Seems that was blocking it somehow.
Looking forward to try this out :)