GNU bug report logs - #18742
gnunet intermittently fails its test suite on all platforms

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18742 in the body.
You can then email your comments to 18742 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: bug-guix <at> gnu.org
Subject: gnunet intermittently fails its test suite on all platforms
Date: Wed, 15 Oct 2014 16:33:25 -0400

gnunet intermittently fails its test suite on all platforms.  The
failures are not consistent.  See:

  http://hydra.gnu.org/build/122625/log/raw
  http://hydra.gnu.org/build/82158/log/tail-reload
  http://hydra.gnu.org/build/121802/log/tail-reload

Failures seem to be very rare on i686, occasional on x86_64, and
frequent on mips64el:

  http://hydra.gnu.org/job/gnu/master/gnunet-0.10.0.x86_64-linux
  http://hydra.gnu.org/job/gnu/master/gnunet-0.10.0.i686-linux/all
  http://hydra.gnu.org/job/gnu/master/gnunet-0.10.0.mips64el-linux

      Mark

Message #8 received at 18742 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ngillmann <at> runbox.com>
To: 18742 <at> debbugs.gnu.org
Cc: guix-devel <at> gnu.org
Subject: Re: bug #18742
Date: Tue, 27 Sep 2016 18:21:42 +0000

Leo Famulari <leo <at> famulari.name> writes:

 > However you are replying to these bug reports is changing the "Subject"
 > line to only include the bug number. It's hard to know what the bug is
 > about...

I did not want to reply directly to these specific bugs, which is why I
asked on this list first.

 > On Tue, Sep 27, 2016 at 04:38:03PM +0000, ng0 wrote:
 > > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18742
 > > 
 > > Logs are gone since hydra got reset at least once since October 2014. I
 > [ 2 more citation lines. Click/Enter to show. ]
 > > can not see but only assume that the tests I am currently helping to fix
 > > are different tests than the ones which failed in 2014, as the test
 > > suite for GNUnet was refactored.
 > > Can we close this bug or should I reference this bug in an update commit
 > > if/when the test suite is fixed for Guix builds?

 > It seems to be building or not building (depending on the architecture)
 > consistently. If you are happy with those results, please close the bug
 > :)

I think I can not do this, close bugs I did not create myself. If I am
wrong about this I advise that we write a short appendum for Guix
documentation (part: contributing, new subsection: reporting bugs) which
explains debbugs usage, because upstream or at least the version+online
handbook on gnu.org is simply terrible in getting to the point.


 > https://hydra.gnu.org/search?query=gnunet

Dependencies fail on architecture I do not have available (yet / in a
forseeable future).

I think I'm okay with referencing this bug when/if I can close the
current failing test suite bug.
-- 
              ng0

Message #11 received at 18742 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ngillmann <at> runbox.com>
To: 18742 <at> debbugs.gnu.org
Cc: guix-devel <at> gnu.org
Subject: Re: bug #18742
Date: Fri, 30 Sep 2016 14:52:42 +0000

ng0 <ngillmann <at> runbox.com> writes:

> Leo Famulari <leo <at> famulari.name> writes:
>
>  > However you are replying to these bug reports is changing the "Subject"
>  > line to only include the bug number. It's hard to know what the bug is
>  > about...
>
> I did not want to reply directly to these specific bugs, which is why I
> asked on this list first.
>
>  > On Tue, Sep 27, 2016 at 04:38:03PM +0000, ng0 wrote:
>  > > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18742
>  > > 
>  > > Logs are gone since hydra got reset at least once since October 2014. I
>  > [ 2 more citation lines. Click/Enter to show. ]
>  > > can not see but only assume that the tests I am currently helping to fix
>  > > are different tests than the ones which failed in 2014, as the test
>  > > suite for GNUnet was refactored.
>  > > Can we close this bug or should I reference this bug in an update commit
>  > > if/when the test suite is fixed for Guix builds?
>
>  > It seems to be building or not building (depending on the architecture)
>  > consistently. If you are happy with those results, please close the bug
>  > :)
>
> I think I can not do this, close bugs I did not create myself. If I am
> wrong about this I advise that we write a short appendum for Guix
> documentation (part: contributing, new subsection: reporting bugs) which
> explains debbugs usage, because upstream or at least the version+online
> handbook on gnu.org is simply terrible in getting to the point.
>
>
>  > https://hydra.gnu.org/search?query=gnunet
>
> Dependencies fail on architecture I do not have available (yet / in a
> forseeable future).

Related to this: what are affordable, powerful (should at least be able
to bootstrap any X11 based system) hardware systems for arm and mips
where people build Guix on?

> I think I'm okay with referencing this bug when/if I can close the
> current failing test suite bug.
> -- 
>               ng0
>
>

-- 

Message #14 received at 18742 <at> debbugs.gnu.org (full text, mbox):

From: Joshua Branson <bransoj <at> hotmail.com>
To: "18742 <at> debbugs.gnu.org" <18742 <at> debbugs.gnu.org>
Subject: gunner intermittently fails its test suit on all platforms
Date: Fri, 17 Mar 2017 19:42:43 +0000

This seems to be partially resolved.  gnunet is now at version 0.10.1.  And both i686 and X86_64 normally build correctly.  Though there were two recent fails on both builds.  

mips64el is failing a lot.  I don’t see a correct build yet.

Joshua

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.