On Jun 1, 2012 3:56 AM, "Bert Huijben" <bert_at_qqmail.nl> wrote:
>
>
>
> > -----Original Message-----
> > From: Greg Stein [mailto:gstein_at_gmail.com]
> > Sent: vrijdag 1 juni 2012 9:28
> > To: dev_at_subversion.apache.org
> > Subject: validity check error? huh?
> >
> > Any ideas on why I'm seeing this now?
> >
> >
> > $ ./basic_tests.py 1
> > W: subversion/svn/delete-cmd.c:92: (apr_err=200035)
> > W: subversion/svn/util.c:913: (apr_err=200035)
> > W: subversion/libsvn_client/delete.c:482: (apr_err=200035)
> > W: subversion/libsvn_client/delete.c:383: (apr_err=200035)
> > W: subversion/libsvn_wc/adm_ops.c:701: (apr_err=200035)
> > W: subversion/libsvn_wc/wc_db.c:6974: (apr_err=200035)
> > W: subversion/libsvn_wc/wc_db.c:2595: (apr_err=200035)
> > W: subversion/libsvn_wc/wc_db_util.c:202: (apr_err=200035)
> > W: subversion/libsvn_subr/sqlite.c:1060: (apr_err=200035)
> > W: subversion/libsvn_wc/wc_db_util.c:185: (apr_err=200035)
> > W: subversion/libsvn_wc/wc_db.c:6795: (apr_err=200035)
> > W: subversion/libsvn_wc/wc_db.c:6734: (apr_err=200035)
> > W: subversion/libsvn_subr/sqlite.c:251: (apr_err=200035)
> > W: subversion/libsvn_subr/sqlite.c:235: (apr_err=200035)
> > W: subversion/libsvn_subr/sqlite.c:271: (apr_err=200035)
> > W: svn: E200035: sqlite: constraint failed
> > W: subversion/libsvn_subr/sqlite.c:607: (apr_err=200035)
> > W: svn: E200035: sqlite: WC DB validity check 03 failed
> >
> >
> > That's ra_local to fsfs.
>
> One of the buildbots had this too before upgrading its Sqlite.
>
> The WC-DB validations assume that the database is consistent at all times,
> while the Sqlite queries that update the database assume that the database
> is consistent between queries.
>
> There are differences between those assumptions if an UPDATE or INSERT
uses
> a different index than expected.
So you're suggesting that I need to update sqlite? I'm currently using a
3.7.5 in-tree amalgamation. (Pending a non-obvious build/link error)
Assuming yes on upgrade, then do you also recommend that I step-wise
upgrade to determine our new minimum requirement, or do you already know
it? (and if so, why is that not already encoded into our build system) ...
happy to help discover; just need some direction.
Are there any changes to triggers? Will 1.8 continue to work on a 1.7
wc.db? Or do we have some kind of change in triggers that is causing a
problem?
Cheers,
-g
Received on 2012-06-01 10:11:14 CEST