Add blob support to the unitytls backend #48
jy-vivoxmacos.yml
on: pull_request
Matrix: autotools
Matrix: cmake
Matrix: combinations
Annotations
142 errors and 2 warnings
|
CM llvm@15 macos-14 SecureTransport
Process completed with exit code 2.
|
|
AM clang LibreSSL
Process completed with exit code 1.
|
|
AM clang LibreSSL
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang LibreSSL
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang LibreSSL
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL libssh2 !ldap 10.15
Process completed with exit code 1.
|
|
AM clang OpenSSL libssh2 !ldap 10.15
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL libssh2 !ldap 10.15
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL libssh2 !ldap 10.15
invalid option: --no-lock
Did you mean? no-go
|
|
AM llvm@15 macos-14 SecureTransport
Process completed with exit code 1.
|
|
AM llvm@15 macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
AM llvm@15 macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
AM llvm@15 macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 wolfSSL !ldap brotli zstd
Process completed with exit code 1.
|
|
CM clang OpenSSL ws gsasl AppleIDN
Process completed with exit code 1.
|
|
CM gcc-12 wolfSSL !ldap brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang OpenSSL ws gsasl AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 wolfSSL !ldap brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang OpenSSL ws gsasl AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 wolfSSL !ldap brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang OpenSSL ws gsasl AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL libssh c-ares
Process completed with exit code 1.
|
|
AM clang OpenSSL libssh c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL libssh c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL torture !FTP
Process completed with exit code 1.
|
|
AM clang OpenSSL libssh c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL torture !FTP
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL torture !FTP
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL torture !FTP
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang macos-14 SecureTransport
Process completed with exit code 1.
|
|
AM clang macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-12 !ssl !debug
Process completed with exit code 1.
|
|
AM gcc-12 !ssl !debug
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-12 !ssl !debug
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-12 !ssl !debug
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang OpenSSL +static libssh
Process completed with exit code 1.
|
|
CM clang OpenSSL +static libssh
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang OpenSSL +static libssh
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang OpenSSL +static libssh
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl libssh2 AppleIDN
Process completed with exit code 1.
|
|
AM clang !ssl libssh2 AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl libssh2 AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl libssh2 AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang SecureTransport ws debug+
Process completed with exit code 1.
|
|
CM clang SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 SecureTransport ws debug+
Process completed with exit code 1.
|
|
CM gcc-12 SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-13 macos-14 SecureTransport
Process completed with exit code 1.
|
|
AM gcc-13 macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-13 macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-13 macos-14 SecureTransport
invalid option: --no-lock
Did you mean? no-go
|
|
CM llvm@15 SecureTransport ws debug+
Process completed with exit code 1.
|
|
CM llvm@15 SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
CM llvm@15 SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
CM llvm@15 SecureTransport ws debug+
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl !debug brotli zstd
Process completed with exit code 1.
|
|
AM clang !ssl !debug brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl !debug brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl !debug brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL torture FTP
Process completed with exit code 1.
|
|
AM clang OpenSSL torture FTP
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL torture FTP
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL torture FTP
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang SecureTransport libssh2 10.12
Process completed with exit code 1.
|
|
AM clang SecureTransport libssh2 10.12
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang SecureTransport libssh2 10.12
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang SecureTransport libssh2 10.12
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL
Process completed with exit code 1.
|
|
AM clang OpenSSL
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang wolfSSL !ldap brotli zstd
Process completed with exit code 1.
|
|
CM clang wolfSSL !ldap brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang wolfSSL !ldap brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang wolfSSL !ldap brotli zstd
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-12 SecureTransport libssh2
Process completed with exit code 1.
|
|
AM gcc-12 SecureTransport libssh2
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-12 SecureTransport libssh2
invalid option: --no-lock
Did you mean? no-go
|
|
AM gcc-12 SecureTransport libssh2
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl
Process completed with exit code 1.
|
|
AM clang !ssl
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 GnuTLS !ldap krb5
Process completed with exit code 1.
|
|
CM gcc-12 GnuTLS !ldap krb5
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 GnuTLS !ldap krb5
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 GnuTLS !ldap krb5
invalid option: --no-lock
Did you mean? no-go
|
|
AM llvm@15 OpenSSL libssh
Process completed with exit code 1.
|
|
AM llvm@15 OpenSSL libssh
invalid option: --no-lock
Did you mean? no-go
|
|
AM llvm@15 OpenSSL libssh
invalid option: --no-lock
Did you mean? no-go
|
|
AM llvm@15 OpenSSL libssh
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang GnuTLS !ldap krb5
Process completed with exit code 1.
|
|
CM clang GnuTLS !ldap krb5
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang GnuTLS !ldap krb5
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang GnuTLS !ldap krb5
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl HTTP-only
Process completed with exit code 1.
|
|
AM clang !ssl HTTP-only
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl HTTP-only
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl HTTP-only
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang LibreSSL !ldap heimdal c-ares
Process completed with exit code 1.
|
|
CM clang LibreSSL !ldap heimdal c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang LibreSSL !ldap heimdal c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang LibreSSL !ldap heimdal c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL event-based
Process completed with exit code 1.
|
|
AM clang OpenSSL event-based
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL event-based
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang OpenSSL event-based
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl c-ares
Process completed with exit code 1.
|
|
AM clang !ssl c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang !ssl c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 OpenSSL +static libssh
Process completed with exit code 1.
|
|
CM gcc-12 OpenSSL +static libssh
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 OpenSSL +static libssh
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 OpenSSL +static libssh
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang SecureTransport libssh2
Process completed with exit code 1.
|
|
AM clang SecureTransport libssh2
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang SecureTransport libssh2
invalid option: --no-lock
Did you mean? no-go
|
|
AM clang SecureTransport libssh2
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 OpenSSL ws gsasl AppleIDN
Process completed with exit code 1.
|
|
CM gcc-12 OpenSSL ws gsasl AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 OpenSSL ws gsasl AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 OpenSSL ws gsasl AppleIDN
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 LibreSSL !ldap heimdal c-ares
Process completed with exit code 1.
|
|
CM gcc-12 LibreSSL !ldap heimdal c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 LibreSSL !ldap heimdal c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
CM gcc-12 LibreSSL !ldap heimdal c-ares
invalid option: --no-lock
Did you mean? no-go
|
|
CM clang macos-12 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
CM llvm@15 macos-12 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
AM clang macos-13 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
AM gcc-13 macos-12 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
AM llvm@15 macos-13 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
AM llvm@15 macos-12 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
CM llvm@15 macos-13 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
CM clang macos-13 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
AM clang macos-12 SecureTransport
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
CM llvm@15 macos-14 SecureTransport
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
CM clang macos-14 SecureTransport
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|