Bug#668025: mercurial: FTBFS[kfreebsd-amd64]: testsuite failure

2012-04-11 Thread Julien Cristau
On Tue, Apr 10, 2012 at 08:14:58 +0100, Javi Merino wrote:

 On Tue, Apr 10, 2012 at 08:21:00AM +0200, Julien Cristau wrote:
  On Sun, Apr  8, 2012 at 13:27:03 +0200, Christoph Egger wrote:
  
   Your package failed to build on the kfreebsd-amd64 buildds:
   
   --- 
   /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
   +++ 
   /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t.err
   @@ -29,7 +29,6 @@
  $ rm b
  $ echo foo  b
  $ hg --config extensions.n=$TESTTMP/nolink.py status --debug
   -  ignoring suspect symlink placeholder b

Make a clone using placeholders:

   
   ERROR: 
   /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
output changed
   
  Out of 4 tries on kfreebsd-amd64 for this version, it failed 3 times on
  3 different tests, and succeeded on the fourth build.  Not sure I
  understand this particular one, but I think it's more likely to be an
  unreliable test than a new bug.
 
 None of the changes from 2.1.2-1 to 2.1.2-2 should affect these tests, so
 that's actually 2 successful builds out of 5.  On some architectures the
 testsuite is unreliable.  If this happens again, I'll probably stop
 running it on kfreebsd-amd64.  
 
FWIW, same failure at
http://hgbuildbot.kublai.com/builders/OS%20X%2010.6%20hg%20tests/builds/106/steps/run-tests.py%20%28python2.7%29/logs/stdio
I don't think it's an architecture issue.

Cheers,
Julien



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#668025: mercurial: FTBFS[kfreebsd-amd64]: testsuite failure

2012-04-10 Thread Julien Cristau
On Sun, Apr  8, 2012 at 13:27:03 +0200, Christoph Egger wrote:

 Your package failed to build on the kfreebsd-amd64 buildds:
 
 --- 
 /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
 +++ 
 /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t.err
 @@ -29,7 +29,6 @@
$ rm b
$ echo foo  b
$ hg --config extensions.n=$TESTTMP/nolink.py status --debug
 -  ignoring suspect symlink placeholder b
  
  Make a clone using placeholders:
  
 
 ERROR: 
 /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
  output changed
 
Out of 4 tries on kfreebsd-amd64 for this version, it failed 3 times on
3 different tests, and succeeded on the fourth build.  Not sure I
understand this particular one, but I think it's more likely to be an
unreliable test than a new bug.

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#668025: mercurial: FTBFS[kfreebsd-amd64]: testsuite failure

2012-04-10 Thread Javi Merino
On Tue, Apr 10, 2012 at 08:21:00AM +0200, Julien Cristau wrote:
 On Sun, Apr  8, 2012 at 13:27:03 +0200, Christoph Egger wrote:
 
  Your package failed to build on the kfreebsd-amd64 buildds:
  
  --- 
  /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
  +++ 
  /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t.err
  @@ -29,7 +29,6 @@
 $ rm b
 $ echo foo  b
 $ hg --config extensions.n=$TESTTMP/nolink.py status --debug
  -  ignoring suspect symlink placeholder b
   
   Make a clone using placeholders:
   
  
  ERROR: 
  /build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
   output changed
  
 Out of 4 tries on kfreebsd-amd64 for this version, it failed 3 times on
 3 different tests, and succeeded on the fourth build.  Not sure I
 understand this particular one, but I think it's more likely to be an
 unreliable test than a new bug.

None of the changes from 2.1.2-1 to 2.1.2-2 should affect these tests, so
that's actually 2 successful builds out of 5.  On some architectures the
testsuite is unreliable.  If this happens again, I'll probably stop
running it on kfreebsd-amd64.  

Cheers,
Javi



signature.asc
Description: Digital signature


Bug#668025: mercurial: FTBFS[kfreebsd-amd64]: testsuite failure

2012-04-08 Thread Christoph Egger
Package: src:mercurial
Version: 2.1.2-2
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-amd64 buildds:

--- 
/build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
+++ 
/build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t.err
@@ -29,7 +29,6 @@
   $ rm b
   $ echo foo  b
   $ hg --config extensions.n=$TESTTMP/nolink.py status --debug
-  ignoring suspect symlink placeholder b
 
 Make a clone using placeholders:
 

ERROR: 
/build/buildd-mercurial_2.1.2-2-kfreebsd-amd64-aq2Wfm/mercurial-2.1.2/tests/test-symlink-placeholder.t
 output changed

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=mercurialarch=kfreebsd-amd64ver=2.1.2-2stamp=1333748687

Regards

Christoph

If you have further questions please mail debian-...@lists.debian.org

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org