BRD-20938 - temp workaround to enable unit tests to run on scorm_engine #276
build.yml
on: push
Matrix: tests
build-deploy-docs
0s
Annotations
30 errors and 24 warnings
|
tests (macos-latest-large, 3.2)
The current runner (macos--x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.2.3 /Users/runner/hostedtoolcache/Ruby/3.2.3/x64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.2.3/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest, 3.3)
The current runner (macos--arm64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.3.0 /Users/runner/hostedtoolcache/Ruby/3.3.0/arm64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.3.0/arm64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest-large, 3)
The current runner (macos--x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.3.0 /Users/runner/hostedtoolcache/Ruby/3.3.0/x64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.3.0/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest-large, 3.3)
The current runner (macos--x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.3.0 /Users/runner/hostedtoolcache/Ruby/3.3.0/x64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.3.0/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest-large, 3.1)
The current runner (macos--x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.1.4 /Users/runner/hostedtoolcache/Ruby/3.1.4/x64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.1.4/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest-large, 2.7)
The current runner (macos--x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 2.7.8 /Users/runner/hostedtoolcache/Ruby/2.7.8/x64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/2.7.8/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest-large, head)
The current runner (macos--x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build head /Users/runner/hostedtoolcache/Ruby/head/x64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/head/x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest, head)
The current runner (macos--arm64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build head /Users/runner/hostedtoolcache/Ruby/head/arm64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/head/arm64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest, 2.7)
The current runner (macos--arm64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 2.7.8 /Users/runner/hostedtoolcache/Ruby/2.7.8/arm64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/2.7.8/arm64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest, 3.1)
The current runner (macos--arm64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.1.4 /Users/runner/hostedtoolcache/Ruby/3.1.4/arm64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.1.4/arm64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest, 3.2)
The current runner (macos--arm64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.2.3 /Users/runner/hostedtoolcache/Ruby/3.2.3/arm64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.2.3/arm64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (macos-latest, 3)
The current runner (macos--arm64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 3.3.0 /Users/runner/hostedtoolcache/Ruby/3.3.0/arm64
Once that completes successfully, mark it as complete with:
$ touch /Users/runner/hostedtoolcache/Ruby/3.3.0/arm64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
tests (ubuntu-22.04, head)
Process completed with exit code 1.
|
|
tests (ubuntu-22.04, 3.2)
Process completed with exit code 1.
|
|
tests (ubuntu-22.04, 3.1)
Process completed with exit code 1.
|
|
tests (ubuntu-22.04, 3)
Process completed with exit code 1.
|
|
tests (macos-13, 3.3)
Process completed with exit code 1.
|
|
tests (ubuntu-22.04, 3.3)
Process completed with exit code 1.
|
|
tests (macos-13, head)
Process completed with exit code 1.
|
|
tests (macos-13, 3.1)
Process completed with exit code 1.
|
|
tests (macos-13, 3.2)
Process completed with exit code 1.
|
|
tests (macos-13, 3)
Process completed with exit code 1.
|
|
tests (ubuntu-22.04, 2.7)
Process completed with exit code 1.
|
|
tests (macos-13, 2.7)
Process completed with exit code 1.
|
|
tests (ubuntu-20.04, head)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
tests (ubuntu-20.04, 3)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
tests (ubuntu-20.04, 3.3)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
tests (ubuntu-20.04, 3.2)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
tests (ubuntu-20.04, 3.1)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
tests (ubuntu-20.04, 2.7)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
tests (ubuntu-22.04, head)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0lKPBaAAAAADAwJgFsC3hQYOSUICcrr7KQ0hJMzBFREdFMDQxNwBFZGdl
|
|
tests (ubuntu-22.04, head)
Failed to restore: Cache service responded with 400
|
|
tests (ubuntu-22.04, 3.2)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0lqPBaAAAAACatkZPpXdyTr85JPSbj6PzQ0hJMzBFREdFMDIxNgBFZGdl
|
|
tests (ubuntu-22.04, 3.2)
Failed to restore: Cache service responded with 400
|
|
tests (ubuntu-22.04, 3.1)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0lqPBaAAAAADv0HG4x50pRYuTfX2LJ5RqQkwyQUEyMDMwMTA2MDA3AEVkZ2U=
|
|
tests (ubuntu-22.04, 3.1)
Failed to restore: Cache service responded with 400
|
|
tests (ubuntu-22.04, 3)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0l6PBaAAAAABPd0DSBogCR6yJVRSHMF9qQ0hJMzBFREdFMDQxMQBFZGdl
|
|
tests (ubuntu-22.04, 3)
Failed to restore: Cache service responded with 400
|
|
tests (macos-13, 3.3)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mqPBaAAAAAAeAepyLAnpRITdi8fC0DXLQkwyQUEyMDMwMTA1MDM1AEVkZ2U=
|
|
tests (ubuntu-22.04, 3.3)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0m6PBaAAAAACjxeecJyy1RoLVnrmZIG+mQ0hJMzBFREdFMDIwNwBFZGdl
|
|
tests (ubuntu-22.04, 3.3)
Failed to restore: Cache service responded with 400
|
|
tests (macos-13, 3.3)
Failed to restore: Cache service responded with 400
|
|
tests (macos-13, head)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0nKPBaAAAAAAV5HrNAMcEQZG2UMs4R2r0QkwyQUEyMDMwMTA2MDQ1AEVkZ2U=
|
|
tests (macos-13, head)
Failed to restore: Cache service responded with 400
|
|
tests (macos-13, 3.1)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0m6PBaAAAAAD0oL/EmGV2Sq+mY4wgOk3WQkwyQUEyMDMwMTEwMDA3AEVkZ2U=
|
|
tests (macos-13, 3.1)
Failed to restore: Cache service responded with 400
|
|
tests (macos-13, 3.2)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0naPBaAAAAAB404D4BRUmQ7RwXKOXjaXpQkwyQUEyMDMwMTEwMDQ5AEVkZ2U=
|
|
tests (macos-13, 3.2)
Failed to restore: Cache service responded with 400
|
|
tests (macos-13, 3)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0oaPBaAAAAABZiHyL10VcRqDi3Mhebx3IQkwyQUEyMDMwMTA2MDExAEVkZ2U=
|
|
tests (macos-13, 3)
Failed to restore: Cache service responded with 400
|
|
tests (ubuntu-22.04, 2.7)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0qqPBaAAAAAAarV0iuVtxQ4xE3LonUxvTREVOMzAxMDAwMTA3MDIxAEVkZ2U=
|
|
tests (ubuntu-22.04, 2.7)
Failed to restore: Cache service responded with 400
|
|
tests (macos-13, 2.7)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>02KPBaAAAAAB0maws1zejQ6+tRp5ennzQQkwyQUEyMDMwMTA3MDI1AEVkZ2U=
|
|
tests (macos-13, 2.7)
Failed to restore: Cache service responded with 400
|