2009/12/1 Julian Foad <julian.foad_at_wandisco.com>:
> julianf: hey folks: I get a wierd error trying to commit "Wimp" status
> for that failing test (basic_tests 7):
> julianf: svn: The specified baseline is not the latest baseline, so it
> may not be checked out.
> julianf: svn: Your commit message was left in a temporary file:
> hwright: what's a "baseline"?
> julianf: I guess it means "your BASE revision" (pristine).
> julianf: I've updated, of course, and all looks fine:
> julianf: $ svn st -uv subversion/tests/cmdline/basic_tests.py
> julianf: M 885821 885378 julianfoad
> subversion/tests/cmdline/basic_tests.py
> julianf: Status against revision: 885821
> julianf: Trying to find out if there's something wierd about the
> particular dev build I'm using.
> cmpilato: 'baseline' is a WebDAV term.
> cmpilato: and yeah, that's an out-of-date error in so many words.
> julianf: cmpilato/anyone: I'm at a loss what to do about that "baseline"
> error.
> cmpilato: julianf: i usually just cry.
> julianf: can't commit. Haven't re-built my client since last successful
> commit. Have updated the WC.
> cmpilato: and sip chamomile tea.
> cmpilato: got interfering/stale wcprops?
> * julianf doesn't understand.
> julianf: wcprops?
> cmpilato: dav props?
> julianf: I've heard of them. How would I get them / find them?
> cmpilato: those seekr1t little buggers that the dav layers use to cache
> stuff like "the revision of this thing"
> cmpilato: using 1.6?
> cmpilato: or trunk client?
> julianf: no, trunk yesterday opr so
> cmpilato: then the wcprops live in the wc db.
> cmpilato: i don't have the incantations on hand to examine that, but
> that's what i'd recommend.
> julianf: maybe wc is hosed... will try diff/patching the change I want
> to commit onto A different WC...
> cmpilato: "wc is hosed" isn't something we prefer to just write off as
> business-as-usual, of course.
> cmpilato: (though i certainly feel your pain... sub*cough* *hack*athon)
> CIA-66: julianfoad *
> r885840 /trunk/subversion/tests/cmdline/basic_tests.py: Mark
> basic_tests.py 7 as "Wimp" because it's currently a known failure. ...
> julianf: hah, that worked.
> julianf: So my WC was "hosed" in some sense.
> julianf: cmpilato: thanks for the clue that it was a WC problem. I
> hadn't guessed that from the error message & symptoms.
> cmpilato: have you preserved the busted WC?
> julianf: I traced it through 5 re-tries of "get latest baseline". It
> thought it was out of date, but wasn't, so maybe a bug there. I was (and
> am) using Neon, BTW.
> julianf: Yes I have the WC.
> julianf: I could make it available.
> cmpilato: that'd be cool.
> julianf: cmpilato/anyone:
> <http://filebin.ca/zyoef/subversion-c-testdir.tgz>
> julianf: WC on which "commit" says "baseline" is out of date but isn't.
> Maybe spurious DAV-props?
> lisppaste4: cmpilato pasted "Julian's davprops" at
> http://paste.lisp.org/display/91367
> * cmpilato wonders if 'svn cleanup' should purge the dav_cache ...
> cmpilato: still, in this case the version-urls for basic_tests.py and
> its parent directory reflect that most-recent-at-the-time changes of
> those items. weird.
> julianf: cmpilato/anyone:
> <http://filebin.ca/benyyk/subversion-c-whole.tgz> is the whole WC of
> which the previous was a subdir.
> julianf: (Don't know if that shows you anything more.)
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2425948
>
> Please start new threads on the <dev_at_subversion.apache.org> mailing list.
> To subscribe to the new list, send an empty e-mail to <dev-subscribe_at_subversion.apache.org>.
>
Regarding the "The specified baseline is not the latest baseline, so
it may not be checked out." message:
ASF has two Subversion hosts, one in EU and another in US. The EU one
acts as a write-through proxy. The above message is displayed when the
EU slave happens to be several revisions behind the US master.
It is rare, but it happens. I just experienced it when trying to
commit at 12:59:54 MSK. I think that the following commit was causing
the delay that I observed:
http://svn.apache.org/viewvc?view=revision&revision=891611
The mitigation is to wait a minute and retry your commit.
The "Reopen commit dialog after a commit failed" option in TortoiseSVN
helps here.
Best regards,
Konstantin Kolinko
Original thread at dev_at_s.t.o:
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2425948
Received on 2009-12-17 11:19:37 CET