Unexpected Error #2
Hi there, This is an update to my previous email. I re-executed the same build after rolling back Subversion to v1.8.8 (from 1.8.9), performing a TortoiseSvn Cleanup and got the following error message when the build failed again. I don't know if this is a red herring or not but I thought it was worth mentioning. Regards Andrew === [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:perform (default-cli) on project onlinebanking: Unable to checkout from SCM [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E175012: Connection timed out [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. __ The contents of this email and any attachments are confidential and may be legally privileged. If you are not the intended recipient please advise the sender immediately and delete the email and attachments. Any use, dissemination, reproduction or distribution of this email and any attachments by anyone other than the intended recipient is prohibited.
Unexpected Error
Hi there, I received the following error during a build and have attached the log and dump files as suggested, any support would be appreciated. Details System : Windows Server 2003 R2, Intel Xeon 3.06GHz, 4GB RAM with plenty of available storage. Java project built using CruiseControl v2.7.2, Maven 3.1.1 and JDK 1.6.0_45. Subversion and CruiseControl servers are in different locations and both have v1.8.9 of Subversion. Please let me know if there is any more information you need. Thanks and regards Andrew Maven build.log snippet [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:07.578s [INFO] Finished at: Mon Jun 16 09:25:59 NZST 2014 [INFO] Final Memory: 19M/742M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.2:perform (default-cli) on project onlinebanking: Unable to checkout from SCM [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [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:\DOCUME~1\SRV-CL~1\LOCALS~1\Temp\svn-crash-log20140616092558.log [ERROR] C:\DOCUME~1\SRV-CL~1\LOCALS~1\Temp\svn-crash-log20140616092558.dmp [ERROR] Please send the log file to users@subversion.apache.org to help us analyze [ERROR] and solve this problem. Generated log files __ The contents of this email and any attachments are confidential and may be legally privileged. If you are not the intended recipient please advise the sender immediately and delete the email and attachments. Any use, dissemination, reproduction or distribution of this email and any attachments by anyone other than the intended recipient is prohibited. svn-crash-log20140616092558.log Description: Binary data svn-crash-log20140616092558.dmp Description: Binary data
TortoiseSVN bug - assertion failure
In file 'D:\Development\SVN\Releases\TortoiseSVN-1.8.7\ext\subversion\subversion\libsvn_wc\wc_db.c' line 13676: assertion failed (svn_dirent_is_absolute(local_abspath)) --- OK --- The circumstances involving the assertion were as follows: 1) In repo-browser, I created a folder directly under "trunk". 2) I attempted to check this folder out to a directory that already contained actual versionable files (i.e., source files)*. When I attempted the checkout, I got the error. I may revert to an older version of TortoiseSVN, since I've never gotten that error before, and it's preventing me from adding projects (unless I use another technique). [*This is how I add a project to source control. After checking out a new, empty project, I use TortoiseSvn (from the explorer menu) to add the revelevant files, then perform a commit.] I don't know whether I'm sending this post to the correct address, as the instructions for bug reporting are very poorly written. I don't know whether I'm sending this report to the correct place, as the instructions for bug reporting are extremely poor.
