gnunet intermittently fails its test suite on all platforms

DoneSubmitted by Mark H Weaver.
Details
4 participants
  • Joshua Branson
  • Ludovic Courtès
  • Mark H Weaver
  • ng0
Owner
unassigned
Severity
normal
M
M
Mark H Weaver wrote on 15 Oct 2014 22:33
(address . bug-guix@gnu.org)
877g013wfe.fsf@netris.org
N
Re: bug #18742
(address . 18742@debbugs.gnu.org)(address . guix-devel@gnu.org)
877f9xjj9l.fsf@we.make.ritual.n0.is
Leo Famulari <leo@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:
> >
> > 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.



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
N
(address . 18742@debbugs.gnu.org)(address . guix-devel@gnu.org)
87h98xv3r9.fsf@we.make.ritual.n0.is
ng0 <ngillmann@runbox.com> writes:

Toggle quote (36 lines)
> Leo Famulari <leo@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?

Toggle quote (7 lines)
> I think I'm okay with referencing this bug when/if I can close the
> current failing test suite bug.
> --
> ng0
>
>

--
J
J
Joshua Branson wrote on 17 Mar 2017 20:42
gunner intermittently fails its test suit on all platforms
(name . 18742@debbugs.gnu.org)(address . 18742@debbugs.gnu.org)
DM5PR10MB1738BCD3E964CB642D44D359A6390@DM5PR10MB1738.namprd10.prod.outlook.com
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
L
L
Ludovic Courtès wrote on 24 Aug 2019 15:38
control message for bug #18742
(address . control@debbugs.gnu.org)
87wof2wuno.fsf@gnu.org
tags 18742 unreproducible
close 18742
quit
?
Your comment

This issue is archived.

To comment on this conversation send email to 18742@debbugs.gnu.org