webrev failure? (original) (raw)

David Holmes david.holmes at oracle.com
Sun Aug 12 23:56:09 UTC 2012


Reverting to 2.2.1 seems to have fixed things for me.

But I tend not to use the -f option with webrev anyway.

David

On 13/08/2012 7:49 AM, David Holmes wrote:

On 12/08/2012 9:39 PM, Martijn Verburg wrote:

Aha! :-). Any ideas on how far I need to downgrade the version of hg? (I'm 2.3 at the moment). Unfortunately no. I just hit this myself with 2.3: > hg --version *** failed to import extension hgext.forest from ~/hg/forest.py: 'module' object has no attribute 'wirerepository' Mercurial Distributed SCM (version 2.3) but I don't know what version I had previously been using. David -----

Cheers, Martijn

On 12 August 2012 12:29, David Holmes<david.holmes at oracle.com> wrote: I had thought that webrev only tried to operate on a forest if you asked it to - and that that requires the forest extension.

That said the forest extension is not working with recent mercurial versions. :( David

On 12/08/2012 2:04 AM, Martijn Verburg wrote: Hi all, Apologies if these are the wrong mailing lists, but I'm assuming that the webrev tool falls under this domain somewhat. In order to get patches into the OpenJDK as cleanly as possible, we're looking to utilise webrev (since it's the std and all). Running "ksh ./make/scripts/webrev.ksh -f" over the latest jdk8/tl source (no patches, but a full build was completed using build-infra) and I got a host of errors: -------- SCM detected: mercurial hg: unknown command 'foutgoing' abort: cannot follow file not in parent revision: "Mercurial" abort: cannot follow file not in parent revision: "basic" abort: cannot follow file not in parent revision: "add" abort: cannot follow file not in parent revision: "annotate" .. .. -------- A separate, yet related set of errors are at http://pastebin.com/q0tF1A4m for sake of brevity in this mail. I assume I'm running this tool incorrectly, I expected a result of something like "You've changed nothing, nothing to se here move along please" :-) Cheers, Martijn



More information about the build-dev mailing list