webrev failure?

Dmitry Samersoff Dmitry.Samersoff at oracle.com
Sun Aug 12 03:39:51 PDT 2012


Martijn,

First step - you need to make
hg st
in your workspace working without extra warning

It looks like something still wrong with your forest extension.

I attached working one and below is two relevant lines from
my ~/.hgrc

[extensions]
forest=/home/dms/.hgext/forest.py

[format]
usefncache=no

-Dmitry


On 2012-08-12 14:16, Martijn Verburg wrote:
> Hi Dmitry,
> 
> Thanks for the hints! After following the forest extension install
> instructions at
> http://hg.openjdk.java.net/jdk7u/jdk7u4/raw-file/tip/README-builds.html#hg
> and running "ksh ./make/scripts/webrev.ksh -N" I get:
> 
> *** failed to import extension forest from forest_extension/forest.py:
> No module named repo
>    SCM detected: mercurial
> *** failed to import extension forest from forest_extension/forest.py:
> No module named repo
> *** failed to import extension forest from forest_extension/forest.py:
> No module named repo
> *** failed to import extension forest from forest_extension/forest.py:
> No module named repo
> 
>  No outgoing, perhaps you haven't commited.
> *** failed to import extension forest from forest_extension/forest.py:
> No module named repo
> *** failed to import extension forest from forest_extension/forest.py:
> No module named repo
> *** failed to import extension forest from forest_extension/forest.py:
> No module named repo
>       Workspace: /Users/karianna/Documents/workspace/jdk8_tl
>       Output to: /Users/karianna/Documents/workspace/jdk8_tl/webrev
>    Output Files:
> 	common/autoconf/configure
> 		 patch cdiffs udiffs sdiffs frames old new
> 	get_source.sh
> 		 patch cdiffs udiffs sdiffs frames old new
>      index.html: Done.
> Output to: /Users/karianna/Documents/workspace/jdk8_tl/webrev
> 
> So I'm a bit unsure about the "*** failed" messages but the "No
> outgoing, perhaps you haven't commited." makes complete sense.
> 
> Do I need to alter forest.py in order to get the list of modules correct?
> 
> Cheers,
> Martijn
> 
> 
> On 11 August 2012 19:52, Dmitry Samersoff <Dmitry.Samersoff at oracle.com> wrote:
>> Martin,
>>
>> 1. Make sure you have a forest extension
>> 2. Try webrev -N to create webrev against your current workspace rather
>>    than against remote repository
>>
>> -Dmitry
>>
>> On 2012-08-11 20:04, 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
>>>
>>
>>
>> --
>> Dmitry Samersoff
>> Java Hotspot development team, SPB04
>> * There will come soft rains ...
>>
>>


-- 
Dmitry Samersoff
Java Hotspot development team, SPB04
* There will come soft rains ...




More information about the build-infra-dev mailing list