Libevent2 port is not passing SSL regression tests

[Oleg Moskalenko]

Hi

Libevent is a very important port that is used in many projects (Chromium and Memcached are among the best known ones).
I installed the latest current version of libevent 2.0.19 (port devel/libevent2) and it seems like it is broken in regard to OpenSSL integration (I use the OpenSSL recent port, which is 1.0.1c version). I filed a bug in libevent community, but may be somebody from FreeBSD community can take a look, because probably FreeBSD is not on high priority list of libevent community and this port affects many other projects. This is my bug report:


Bugs item #3531737, was opened at 2012-06-03 13:35
Message generated for change (Tracker Item Submitted) made by holger67
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=461322&aid=3531737&group_id=50884

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libevent-core
Group: For 2.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Oleg Moskalenko (holger67)
Assigned to: Nobody/Anonymous (nobody)
Summary: "make verify" fails on FreeBSD OpenSSL tests

Initial Comment:
OS: FreeBSD 8.x and 9.x
Libevent versions tested: 2.0.15 and 2.0.19
OpenSSL version: 1.0.1c

During the "make verify" regression tests two tests failed:

...............
regress: ssl/bufferevent_renegotiate_socketpair:
  FAIL regress_ssl.c:335: assert(test_is_done == 1)
  [bufferevent_renegotiate_socketpair FAILED]
ssl/bufferevent_renegotiate_filter:
  FAIL regress_ssl.c:335: assert(test_is_done == 1)
  [bufferevent_renegotiate_filter FAILED]
2/179 TESTS FAILED. (0 skipped)
.................

It happens with kqueue, poll and select I/O engines.

It happens with both 32 bits and 64 bits OS versions.

I am attaching the event-config.h file, generated on my FreeBSD 8.2 32-bits system, just in case if it helps.
I also tested it on FreeBSD 9.0 amd64 64-bits system, the error is exactly the same.

=========================================================================