Hello ,
Seeing this error:
We are also facing this quit often. Have you got it resolved?
We are also facing this quit often. Its very random. I donât have any solution to it.
I am using SVN on Assembla. Can this be reason for the same?
Iâm having the same issues as well with Assembla.
Seeing build fails increasingly often from:
Build Fail Error: Caused by java.net.SocketException: Operation Timed Out
I have a similar issue with assembla too - it was working in the past but I tried a build yesterday and it failed 3 times.
The first fail managed to get some files but then failed like this:
1: Running Prebuild steps
2: Removing bvr
3: Successfully uninstalled bvr-1.2.12
4: 1 gem installed
5: done.
6: bvr 1.2.15
7: bvr-api 0.2.4
8: Checking out a fresh workspace because there's no workspace at /BUILD_PATH/my-company-ltd.mkk.ios_mkk
9: Cleaning local Directory .
10: Checking out https://subversion.assembla.com/svn/mycompany/MKK at revision '2016-08-11T12:58:26.040 -0500'
11: A Assets
12: A Assets/Scenes
13: AU Assets/Scenes/Game_Demo.unity
..... (REMOVED FOR VERBOSITY)
2229: AU Assets/Resources/Prefabs/Buildings/Upgrade_GUI/Soldiers.png
2230: svn: E175002: REPORT request failed on '/svn/mycompany/!svn/vcc/default'
2231: Caused by: java.net.SocketException: Operation timed out
2232: at java.net.SocketInputStream.socketRead0(Native Method)
2233: Caused by: java.io.IOException: Failed to check out https://subversion.assembla.com/svn/mycompany/MKK
2234: svn: E175002: REPORT request failed on '/svn/mycompany/!svn/vcc/default'
2235: Caused by: java.net.SocketException: Operation timed out
2236: at java.net.SocketInputStream.socketRead0(Native Method)
2237: postbuildstatus finished successfully.
2238: Finished: FAILURE
2239:
The second fail had a completely different error:
Running Prebuild steps
2: Removing bvr
3: Successfully uninstalled bvr-1.2.12
4: 1 gem installed
5: done.
6: bvr 1.2.15
7: bvr-api 0.2.4
8: Checking out a fresh workspace because there's no workspace at /BUILD_PATH/my-company-ltd.mkk.ios_mkk
9: Cleaning local Directory .
10: Checking out https://subversion.assembla.com/svn/mycompany/MKK at revision '2016-08-11T14:22:29.555 -0500'
11: ERROR: Failed to check out https://subversion.assembla.com/svn/mycompany/MKK
12: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled
13: FATAL: null
14: postbuildstatus finished successfully.
15: Finished: FAILURE
16:
I see this almost every second build. Itâs quite annoying. I have access to my perforce from multiple computers and have had 0 problems. Something seems up with the cloud build. Would love if this is resolved. I hate having to start another build because of timeout failure.
I get this every build now too, itâs very frustrating and ends up making me feel the cloud build is unreliable - Iâve gone back to local builds now as Iâm not sure whether the cloud build will work or not 
Still seeing mostly build fails. Not a huge issue for us at the time, but wanted to give the update in case itâs useful.
Tried assembla with SVN - gave the same timeout error part way through checking out - also âsvn: E175002: REPORT request failed onâŚâ.
Is the fault with the cloud build system or the source hosts?
We are seeing this as well, and we host our SVN repository locally. It seems to have problem with large files, say over 10 MB or so. Sometimes it synchs them successfully, sometimes it doesnât. Would very much like to see a solution to this before we commit to one of the paid Cloud Build plans.
I have seen a couple of errors with building in Unity cloud build but plenty of times it suceeds as well now so just seems a little bit beta right nowâŚ
Perforce:
and
and
90% of our (hundreds of) builds are just this over and over. I recall the java exception was mentioned back in June and billed as being looked into, but itâs still happening.
I get the first Perforce timeout error you listed (below) about 20% of the time. Itâs very annoying since it counts a build failure and I have to wait through cool-down to get another build started.
I moved the project I was working on to git, no problems since. We do have projects still on p4, and they continue to have the issues⌠last I checked one of our lot was getting the javaexception over and over and over trying to get an OS X build out. I told him to just build locally from now on⌠itâs not time saving.
Same here, weâre using SVN and getting java.net.SocketException: Operation timed out 50% of the time for one project, 100% of the time for another. Really annoying, it makes this service practically useless.
Any update on this 4-month-old issue? We cannot currently use Cloud Build with SVN (hosted by http://www.cloudforge.com/). This means weâre working without automatic testing for team-member commits that break our build. This has cost our team a lot of lost development time. Should we give up on using SVN with Cloud Build or will this be addressed? Thanks.
Hi all,
Please direct message me links to projects in Cloud Build that are experiencing these issues. I have created an improved SVN checkout flow that should resolve most of these problems, that is currently in a pre-release per-project mode while we iron out any remaining edge cases.
Thanks,
-Chris
1 Like
Can anyone tell me how to send a direct message to @unitychrism so I can get our project on the test SVN checkout flow? Iâve tried starting a âconversationâ but not sure if thatâs the same as a direct message?
Thanks