Johan Corveleyn wrote on Sun, Jun 05, 2011 at 20:40:34 +0200:
> Fetching external item into
> 'svn-test-work\working_copies\externals_tests-29\A2\iota':
> svn: E235000: In file '..\..\..\subversion\libsvn_wc\workqueue.c' line
> 672: assertion failed (checksum != NULL)
We ran into this assertion on one of the local working copies on
svn.apache.org, while doing 'svn upgrade && svn update' of an update
that adds two new files (with properties; r795270 in the /repos/infra
repository) using an 1.7.0-rc1 'svn' binary. The working copy was
at format 10 before the upgrade.
If I rsync the working copy to my workstation and run 'cleanup' on it
using my trunk@HEAD build, I can reproduce the assertion:
[[[
% $svn cleanup
subversion/libsvn_wc/workqueue.c:672: (apr_err=235000)
svn: E235000: In file 'subversion/libsvn_wc/workqueue.c' line 672: assertion
failed (checksum != NULL)
zsh: abort $SVN cleanup
% svnqlite3-dump | grep -i queue
CREATE TABLE WORK_QUEUE ( id INTEGER PRIMARY KEY AUTOINCREMENT, work BLOB
NOT NULL );
INSERT INTO "WORK_QUEUE" VALUES(5,(file-install
filter.d/asf-svn-abuse-warn.conf 1 0 1 1));
INSERT INTO "WORK_QUEUE" VALUES(6,(file-install filter.d/asf-svn-abuse-ban.conf
1 0 1 1));
INSERT INTO "sqlite_sequence" VALUES('WORK_QUEUE',6);
]]]
However, I haven't found a way to reproduce an 'svn upgrade' scenario
that triggers the assertion.
Does that sound like a bug in rc1 that have been fixed or like an
outstanding bug in trunk? I can share the failing-to-cleanup working
copy privately (27KB .tar.gz).
Thanks,
Daniel
