[tor-bugs] #25942 [Core Tor/Tor]: Fix win32 test failure for crypto/openssl_version

[Tor Bug Tracker & Wiki]

#25942: Fix win32 test failure for crypto/openssl_version
--------------------------------------------+------------------------------
 Reporter:  isis                            |          Owner:  (none)
     Type:  defect                          |         Status:  new
 Priority:  Medium                          |      Milestone:
Component:  Core Tor/Tor                    |        Version:  Tor:
                                            |  0.3.3.5-rc
 Severity:  Normal                          |     Resolution:
 Keywords:  tor-ci tor-windows tor-testing  |  Actual Points:
Parent ID:                                  |         Points:  1
 Reviewer:                                  |        Sponsor:
--------------------------------------------+------------------------------

Comment (by isis):

 Replying to [comment:3 nickm]:
 > So, does that mean we should we revert the build-our-own libevent
 change?

 Eh… that apparently means going back to using pacman, which—due to Arch's
 Terrible Ideas About Operating Systems—means there's no way to specify a
 version (since Arch/pacman have "rolling releases"). So that would mean at
 some point in the future we'd end up with a different libevent on the CI
 machines, which I think generally moving parts in CI is bad? The caching
 should kick in once we have a successful build, and then IIUC we shouldn't
 have to build libevent ever again until we change the git tag listed in
 the `.appveyor-libevent-version` file.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25942#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online