Skip to content
judoscale-ruby tests

Use the configured log level even if the logger has already been initialized #210

Sign in to view logs

Use the configured log level even if the logger has already been initialized

Use the configured log level even if the logger has already been initialized #210

Triggered via pull request December 8, 2023 17:02
@adamlogicadamlogic
opened #190
fix-log-level-config
Status Success
Total duration 1m 15s
Artifacts –

judoscale-ruby-test.yml

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

Annotations

4 warnings
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.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/
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/