Skip to content

Properly handle storing GoodJob data in a non-primary database #185

Properly handle storing GoodJob data in a non-primary database

Properly handle storing GoodJob data in a non-primary database #185

Triggered via pull request August 10, 2023 15:28
Status Failure
Total duration 47s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

judoscale-ruby-test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
test (Gemfile, 3.0)
Process completed with exit code 1.
test (Gemfile, 3.1)
Process completed with exit code 1.
test (Gemfile, 2.7)
Process completed with exit code 1.
test (Gemfile, 2.6)
Process completed with exit code 1.
test (Gemfile, 3.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (Gemfile, 3.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (Gemfile, 2.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (Gemfile, 2.6)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/