Re: workqueue.c line 672: assertion failed (checksum !=NULL)
No, he meant your working copy is corrupted and you need to check out another. The working copy upgrade process cannot handle certain types of working copy corruption. I tried it, I checked out my project again (several gigabytes!) and I encountered problems again. A colleague did the same migration but his project doesn't have externals while mine has tons of 'em. I think there may be an issue with the updating of directories from 1.6.x to 1.7.1 especially in the handling of the externals references. Anyway I went back to 1.6.x and everything's fine for me. -- View this message in context: http://old.nabble.com/workqueue.c-line-672%3A-assertion-failed-%28checksum-%21%3DNULL%29-tp32690129p32875469.html Sent from the Subversion Users mailing list archive at Nabble.com.
Re: workqueue.c line 672: assertion failed (checksum !=NULL)
On Thu, Nov 24, 2011 at 6:27 PM, AlfredD michel.chare...@teledynedalsa.com wrote: No, he meant your working copy is corrupted and you need to check out another. The working copy upgrade process cannot handle certain types of working copy corruption. I tried it, I checked out my project again (several gigabytes!) and I encountered problems again. A colleague did the same migration but his project doesn't have externals while mine has tons of 'em. I think there may be an issue with the updating of directories from 1.6.x to 1.7.1 especially in the handling of the externals references. But as you said, you also encountered this problem with a new checkout (checkout done with 1.7.1 of course). So how can this be upgrade-related? -- Johan
Re: workqueue.c line 672: assertion failed (checksum !=NULL)
Stefan Sperling-7 wrote: Get a new checkout. This problem will be fixed in 1.7.1 which will be released in 4 days or so. I downloaded version 1.7.1 (upgrading from 1.6.something) and the bug's still there... -- View this message in context: http://old.nabble.com/workqueue.c-line-672%3A-assertion-failed-%28checksum-%21%3DNULL%29-tp32690129p32858669.html Sent from the Subversion Users mailing list archive at Nabble.com.
Re: workqueue.c line 672: assertion failed (checksum !=NULL)
On 11/16/2011 4:20 PM, AlfredD wrote: Stefan Sperling-7 wrote: Get a new checkout. This problem will be fixed in 1.7.1 which will be released in 4 days or so. I downloaded version 1.7.1 (upgrading from 1.6.something) and the bug's still there... No, he meant your working copy is corrupted and you need to check out another. The working copy upgrade process cannot handle certain types of working copy corruption. -- David Chapman dcchap...@acm.org Chapman Consulting -- San Jose, CA
workqueue.c line 672: assertion failed (checksum !=NULL)
Trying to update local folder and get this: [cid:image001.png@01CC8F10.F73CD6F0] Cleanup fails. Updates will not work stating a previous process is not complete. It never completes. Stuck! Regards, Michael Bryans inline: image001.png
Re: workqueue.c line 672: assertion failed (checksum !=NULL)
On Thu, Oct 20, 2011 at 02:15:28PM +, Michael Bryans wrote: Trying to update local folder and get this: [cid:image001.png@01CC8F10.F73CD6F0] Cleanup fails. Updates will not work stating a previous process is not complete. It never completes. Stuck! Get a new checkout. This problem will be fixed in 1.7.1 which will be released in 4 days or so.
workqueue.c line 672 assertion failed (checksum != NULL)
Hi, I recently upgraded to subversion 1.7 beta x64, and I got the following error during a submission attempt. My workspace has been locked until I can run cleanup, but when I try I immediately get the same error. Anything I can do? 'D:\Development\SVN\Releases\TortoiseSVN-1.7-beta2\ext\subversion\subversion\libsvn_wc\workqueue.c' Line 672: assertion failed (checksum != NULL)
