Sense.Build fail issue in go-build

2015-07-16 Thread K, Saritha
Hi Team,

Today we got an issue while building Sense.Build in Go-build. This has stopped 
due to an un expected error below .
Please help us on this.

ERROR: This application has halted due to an unexpected error.
ERROR: A crash report and minidump file were saved to disk, you can find them 
here:
ERROR: 
C:\Users\svcArcBuildMan\AppData\Local\Temp\svn-crash-log20150716225021.log
ERROR: 
C:\Users\svcArcBuildMan\AppData\Local\Temp\svn-crash-log20150716225021.dmp
ERROR: Please send the log file to users@subversion.apache.org to help us 
analyze
ERROR: and solve this problem.
ERROR: NOTE: The crash report and minidump files can contain some sensitive 
information
ERROR: (filenames, partial file content, usernames and passwords etc.)
Failed to run svn --username buildman --password ** checkout 
--non-interactive -r 1277 https://wopr.ual.com/svn/sense/trunk 
D:\GoAgent\pipelines\Sense.Build

[go] Job completed Sense.Build/1.0.0.1277/ReviewStage/1/CodeAnalysisJob on 
vcld16gdacvap03 [D:\GoAgent] at Thu Jul 16 22:50:31 CDT 2015



Thanks & Regards
Saritha
+91 7411669493
Email: sarith...@hp.com
 [cid:image003.png@01CFE491.E7CB87A0]





Re: Sense.Build fail issue in go-build

2015-07-16 Thread Ryan Schmidt

On Jul 16, 2015, at 11:18 PM, K, Saritha wrote:

> Today we got an issue while building Sense.Build in Go-build. This has 
> stopped due to an un expected error below .
> Please help us on this.
>  
> ERROR: This application has halted due to an unexpected error.
> ERROR: A crash report and minidump file were saved to disk, you can find them 
> here:
> ERROR: 
> C:\Users\svcArcBuildMan\AppData\Local\Temp\svn-crash-log20150716225021.log
> ERROR: 
> C:\Users\svcArcBuildMan\AppData\Local\Temp\svn-crash-log20150716225021.dmp
> ERROR: Please send the log file to users@subversion.apache.org to help us 
> analyze
> ERROR: and solve this problem.
> ERROR: NOTE: The crash report and minidump files can contain some sensitive 
> information
> ERROR: (filenames, partial file content, usernames and passwords etc.)

Probably, it will be necessary to see the crash report and minidump file 
mentioned above, for anyone to be able to help with this, but heed the warning 
above that they may contain sensitive information.