Re: lib/52007: New failures in lib/libevent/t_event test

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR lib/52007; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: lib/52007: New failures in lib/libevent/t_event test
Date: Mon, 27 Feb 2017 11:55:29 +0700

     Date:        Sun, 26 Feb 2017 11:40:00 +0000 (UTC)
     From:        gson%gson.org@localhost (Andreas Gustafsson)
     Message-ID:  <20170226114000.71DE57A1F9%mollari.NetBSD.org@localhost>
 
   | >How-To-Repeat:
   | Run the ATF tests on a physical machine connected to the Internet.
 
 On amd64 (on a system with ipv6 connectivity, but with much ipv4 firewalled)
 what I see, during the poll test (as you said, kevent & select both work) is:
 
 tc-so:bufferevent/bufferevent_pair_release_lock: [forking] [warn] Trying to disa
 ble lock functions after they have been set up will probaby not work.
 tc-so:[warn] Trying to disable lock functions after they have been set up will p
 robaby not work.
 tc-so:
 tc-so:  FAIL /release/testing/src/external/bsd/libevent/dist/test/regress_buffer
 event.c:270: lock: lock error[err] /release/testing/src/external/bsd/libevent/di
 st/event.c:2557: Assertion evthread_is_debug_lock_held_((base)->th_base_lock) fa
 iled in event_add_nolock_
 tc-so:[Lost connection!]
 tc-so:  [bufferevent_pair_release_lock FAILED]
 
 and then the summary ...
 
 tc-so:1/308 TESTS FAILED. (21 skipped)
 
 Is that what you see too?
 
 
 kre