Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 406801 - dev-libs/libevent src_test(): tests enter infinite loop
Summary: dev-libs/libevent src_test(): tests enter infinite loop
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: All All
: Normal minor (vote)
Assignee: Jeroen Roovers (RETIRED)
URL:
Whiteboard:
Keywords:
: 432878 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-03-03 16:38 UTC by Richard Yao (RETIRED)
Modified: 2012-11-17 21:09 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
dev-libs/libevent-2.0.17 FEATURES=test build.log (build.log,62.77 KB, text/plain)
2012-03-03 16:40 UTC, Richard Yao (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Yao (RETIRED) gentoo-dev 2012-03-03 16:38:21 UTC
When FEATURES=test is set, main/simpletimeout will fail and enter an infinite loop warning about no event_base being set:

main/simpletimeout: 
  FAIL regress_main.c:306: Legacy unit test failed[warn] event_del: event has no event_base set.
[warn] event_del: event has no event_base set.

The build.log file filled a 12GB partition. This was pulled into the dependency graph when trying to compile firefox at Anarchy's request.
Comment 1 Richard Yao (RETIRED) gentoo-dev 2012-03-03 16:40:17 UTC
Created attachment 304139 [details]
dev-libs/libevent-2.0.17 FEATURES=test build.log
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2012-03-15 15:33:23 UTC
Er, it's customary to at least CC package maintainers.
Comment 3 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2012-03-15 16:01:52 UTC
(In reply to comment #2)
> Er, it's customary to at least CC package maintainers.

prefix.g.o is automatically assigned. We will CC maintainers when the bug is triaged and there is something for the maintainer to do or answer. Until then, it is white noise.
Comment 4 Fabian Groffen gentoo-dev 2012-03-15 16:18:06 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Er, it's customary to at least CC package maintainers.
> 
> prefix.g.o is automatically assigned. We will CC maintainers when the bug is
> triaged and there is something for the maintainer to do or answer. Until
> then, it is white noise.

... and, the past has shown that not all maintainers are, let's say, likewise open-minded to engage in a prefix-originated bug.
Comment 5 Jeroen Roovers (RETIRED) gentoo-dev 2012-05-04 17:16:54 UTC
We're two versions onward (not counting the alpha branch) - has this been reported upstream yet?
Comment 6 Richard Yao (RETIRED) gentoo-dev 2012-05-24 20:02:45 UTC
(In reply to comment #5)
> We're two versions onward (not counting the alpha branch) - has this been
> reported upstream yet?

I have not reported it. My hands are tied with race conditions in the Linux kernel and other issues, so reporting this upstream has been a low priority for me.
Comment 7 Jeroen Roovers (RETIRED) gentoo-dev 2012-08-27 10:32:26 UTC
*** Bug 432878 has been marked as a duplicate of this bug. ***
Comment 8 Jeroen Roovers (RETIRED) gentoo-dev 2012-08-27 18:50:23 UTC
This time I will not only prevent the test suite from causing the build to die - I am simply stopping it from running at all. It shouldn't loop like that and certainly not use storage like that, and the problem isn't limited to fringe architectures and operating systems.

# ChangeLog for dev-libs/libevent
# Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-libs/libevent/ChangeLog,v 1.234 2012/08/27 18:48:54 jer Exp $

  27 Aug 2012; Jeroen Roovers <jer@gentoo.org> libevent-2.0.20.ebuild,
  libevent-2.1.1.ebuild:
  Do not run the test suite (bug #406801).

Until upstream takes running their test suite more seriously, this should probably never change again.