[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #32783 [Core Tor/Tor]: Investigate clusterfuzz build failures
#32783: Investigate clusterfuzz build failures
-------------------------------------------------+-------------------------
Reporter: nickm | Owner: nickm
Type: defect | Status:
| assigned
Priority: High | Milestone: Tor:
| 0.4.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: network-team-roadmap-2020Q1, | Actual Points:
security, technical-debt, tor-ci, 043-should |
Parent ID: | Points: 3
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by nickm):
Okay. I spent a lot of time tracking this down, and I believe that the
simplest fix is for us to build our instrumented version of Libevent here
without openssl support, since we don't actually use Libevent's openssl
support.
This bug started happening because Libevent began to require openssl,
unless you explicitly disable it.
This bug became confusing because (I think) Libevent introduced this
requirement while we were suffering from this issue:
https://github.com/google/oss-fuzz/issues/2836 , and so we went from
"failing for one reason where the answer was 'just wait a little'" to
"failing for another reason that needs a fix."
I've made an OSS-Fuzz PR at https://github.com/google/oss-fuzz/issues/2836
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32783#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs