Skip to content

OSX CI builds failing "Please install openssl before running this script" #41006

Closed

Description

@benaadams
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
#41003
#40877

Activity

  1. benaadams commented on Aug 19, 2020

    @benaadams
    MemberAuthor
  2. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Aug 19, 2020
  3. wfurt commented on Aug 19, 2020

    @wfurt
    Member
  4. safern commented on Aug 19, 2020

    @safern
    Member

    Perhaps we're missing to link OpenSSL?

    brew "openssl@1.1"

    cc: @akoeplinger

  5. MattGal commented on Aug 19, 2020

    @MattGal
    Member

    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.

  6. safern commented on Aug 19, 2020

    @safern
    Member

    @MattGal can you help me opening an ICM ticket to figure out what changed in this machines?

  7. MattGal commented on Aug 19, 2020

    @MattGal
    Member

    Ah yes I can do that, let me chat with the team real quick though.

  8. removed
    untriagedNew issue has not been triaged by the area owner
    on Aug 20, 2020
  9. added this to the 6.0.0 milestone on Aug 20, 2020
  10. jaredpar commented on Sep 29, 2020

    @jaredpar
    Member
  11. ghost locked as resolved and limited conversation to collaborators on Dec 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions