We shuffled around our Mercurial repositories last night on our build servers.  
After the move, we're getting errors with two of the repositories on three 
different servers.  In its attempt to find out if anything has changed, CCNet 
is asking Mercurial for the changes between the last build version and the 
latest version.  Unfortunately, the revision number CCNet is using doesn't 
exist.  Here is the debug output [1].  Sure enough, when I log into the server, 
that revision does not exist.

Why is CCnet using the wrong revision number?  Is it pulling it from a file 
somewhere?  I would expect the last call to hg log to be

hg log -b -r 32:31

     <:> Aaron


[1]
[Mercurial] Calling hg parents --template {rev}:
Starting process [hg] in working directory [ReferenceData\] with arguments 
[parents --template {rev}:]
32:
[Mercurial] Calling hg log -b 2012A -r 2012A --template {rev}
Starting process [hg] in working directory [ReferenceData\] with arguments [log 
-b 2012A -r 2012A --template {rev}]
31
[Mercurial] Calling hg log -b 2012A -r 33:31 --style xml -v
abort: unknown revision '33'!



Reply via email to