644904 - Mercurial: m-2.0/m-2.1/m-c report 8 '... not in parents ...' warnings

Status: RESOLVED WORKSFORME

(Infrastructure & Operations :: RelOps: General, task)

Description

[Serge Gautherie (:sgautherie)]

My local commands: (with hg 1.5.4 from mozbuild 1.5.1)
{
hg clone -U -r GECKO_1_9_2_BASE --pull --uncompressed mozilla-1.9.2 mozilla-2.0
cd mozilla-2.0
hg -v verify
// Report is clean so far.

hg pull
hg -v verify
// Something is wrong between GECKO_1_9_2_BASE and tip.
}

Last output:
{
repository uses revlog format 1
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
warning: copy source of 'browser/base/content/tabview/tabitems.js' not in parents of b08bcefd2895
warning: copy source of 'browser/base/content/tabview/tabview.js' not in parents of b08bcefd2895
warning: copy source of 'content/base/test/test_mozfiledataurl.html' not in parents of 2cd506bdbd50
warning: copy source of 'content/media/nsBuiltinDecoderReader.cpp' not in parents of 7519657a1586
warning: copy source of 'content/media/nsBuiltinDecoderReader.h' not in parents of 7519657a1586
warning: copy source of 'content/media/nsBuiltinDecoderStateMachine.cpp' not in parents of 7519657a1586
warning: copy source of 'content/media/nsBuiltinDecoderStateMachine.h' not in parents of 7519657a1586
warning: copy source of 'layout/generic/nsSubDocumentFrame.cpp' not in parents of 8f8d9eb61a5c
71578 files, 63348 changesets, 293656 total revisions
8 warnings encountered!
}

This doesn't seem to break anything on our usual use of this repo(s).
Yet, this should probably be fixed before it gets worse and fwiw anyway.

Ftr, I checked all my local mozilla-related repositories and only "mozilla-central" (and its recent clones) reports issues.

(My local mozilla-central report seems to be worse, but let's (re)start from the beginning.)

***

Can someone confirm?
Are (all) our public repositories verified regularly?

Comment 1

[Zandr Milewski [:zandr]]

These warnings have been there for quite a while, and are harmless:

http://permalink.gmane.org/gmane.comp.version-control.mercurial.general/23195

Comment 2

[Serge Gautherie (:sgautherie)]

(In reply to comment #1)

> These warnings have been there for quite a while, and are harmless:

Ftr, test_mozfiledataurl.html warning is newer than that comment.

And that's what made me wonder initially: these warnings are not ancient days issues but appearing "recently" :-/

> http://permalink.gmane.org/gmane.comp.version-control.mercurial.general/23195

{
[e-mail]
Mercurial SCM general list

Matt Mackall  | 25 Sep 03:35

The warnings mean this repo was started with a now-ancient version of hg
that recorded some copies incorrectly. Which is why they're warnings
rather than errors.
}

Sadly, this doesn't say which "ancient" hg versions was/were affected, nor whether/how anything can/should be done about it.

Fwiw, I would guess "recreating" the repository with manual export+import of the wrongly recorded changesets should restore a clean situation, if there's no easier way. (Yet, hopefully, some "hg debug*" commands could help.)

Comment 3

[Serge Gautherie (:sgautherie)]

(In reply to comment #0)
> (My local mozilla-central report seems to be worse, but let's (re)start from
> the beginning.)

That local repo really was in a worse state :-(

***

My local commands: (with hg 1.5.4 from mozbuild 1.5.1)
{
hg clone -U -r GECKO_2_0_BASE --pull --uncompressed mozilla-2.0 mozilla-central
hg -v verify
// Same 8 warnings, as expected :-|
hg pull
hg -v verify
// Still same 8 warnings. That's good news :-)
}

Then, I just "replaced" my existing m-c repo with this newly recreated one.