Broken macOS tests: latest macOS release 11.2.2 Big Sur has newer OpenSSL and Git versions?

elasticdog / transcrypt

transparently encrypt files within a git repository

MIT License

1.46k stars 102 forks source link

Broken macOS tests: latest macOS release 11.2.2 Big Sur has newer OpenSSL and Git versions? #115

Closed jmurty closed 3 years ago

jmurty commented 3 years ago

This is most likely a problem in GitHub's macos-latest test OS feature, but there is also a chance that the latest macOS release 11.2.2 upgrades OpenSSL and Git in significant ways.

I have been pushing changes and triggering tests tonight, then all of a sudden I started getting strange failures for just the macOS test runs and the following outputs:

OpenSSL version 1.1.1j (my version is LibreSSL 2.8.3 on macOS 11.2.1)
A new hint warning from Git about the default branch name

jmurty commented 3 years ago

The macOS release notes for 11.2.2 are too vague to give any useful details, and the linked web site doesn't (yet) even show 11.2.2 notes for me:

macOS Big Sur 11.2.2 11.2.2 — Restart Required

macOS Big Sur 11.2.2 prevents MacBook Pro (2019 or later) and MacBook Air (2020 or later) models from incurring damage when they are connected to certain third-party, non-compliant powered USB-C hubs and docks.

For more detailed information about this update, please visit: https://support.apple.com/HT211896

jmurty commented 3 years ago

Closing this, the test failures were my user error.

GitHub does use a newer OpenSSL version that is actually provided by default with macOS, so that's something to be wary of in a testing context, but now that I have upgraded to 11.2.2 myself I can confirm that the OpenSSL version provided by Apple by default remains old :(

$ openssl version
LibreSSL 2.8.3

elasticdog commented 3 years ago

Very interesting that GitHub chooses to update the version of OpenSSL on the Mac runners...definitely good to know for future reference.

Related to the hint output, I'd certainly be on board for updating the default branch from master to main. GitHub did recently release their tooling to seamlessly rename branches, so we could do it and not cause too much disruption.