Runtime: OSX CI builds failing "Please install openssl before running this script"

Created on 19 Aug 2020 · 8Comments · Source: dotnet/runtime

Starting: Build CoreCLR Runtime
==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.164.2
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
Script contents:
/Users/runner/work/1/s/src/coreclr/build-runtime.sh checked x64   -ci
========================== Starting Command Output ===========================
/bin/bash --noprofile --norc /Users/runner/work/_temp/13eeaad6-9a45-4642-962d-c1b634862b71.sh
Commencing CoreCLR Repo build
__DistroRid: osx-x64
__RuntimeId: osx-x64
Setting up directories for build
Checking prerequisites...
/usr/local/bin/pkg-config
Please install openssl before running this script, see https://github.com/dotnet/runtime/blob/master/docs/workflow/requirements/macos-requirements.md

##[error]Bash exited with code '1'.
Finishing: Build CoreCLR Runtime

All OSX, iOS, tvOS, etc legs failing with this in
https://github.com/dotnet/runtime/pull/41003
https://github.com/dotnet/runtime/pull/40877

area-Infrastructure blocking-clean-ci

Source

benaadams

All 8 comments

Also
https://github.com/dotnet/runtime/pull/41004
https://github.com/dotnet/runtime/pull/41008

benaadams on 19 Aug 2020

👍1

cc: @MattGal

wfurt on 19 Aug 2020

Perhaps we're missing to link OpenSSL?

https://github.com/dotnet/runtime/blob/60eff3f3766631bd4e7ee256ca17619fec90e9e6/eng/Brewfile#L6

cc: @akoeplinger

safern on 19 Aug 2020

cc: @MattGal

I can't help with _these_ Macs unfortunately, but I would point out that right now (and through 10/1) there's a transition going on with the hosted Azure Devops mac hardware where it's moving from one place (and type of machine) to another; slightly variances there are quite possible. Also, in order for the runtime OpenSSL-based tests to pass, we do absolutely have to link in the two dylibs referenced on the test machines, so something like that is likely in order here.