Skip to content
test

Fix: intervals may not always be started in an async block. #106

Sign in to view logs

Fix: intervals may not always be started in an async block.

Fix: intervals may not always be started in an async block. #106

Triggered via push July 25, 2023 23:46
@dblockdblock
pushed 5f67157
master
Status Success
Total duration 1m 48s
Artifacts –

test-postgresql.yml

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

Annotations

3 warnings
test (ruby=3.1.1, postgresql=14, active_record=~> 7.0.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, GabrielBB/xvfb-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (ruby=3.1.1, postgresql=11, active_record=~> 6.1.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, GabrielBB/xvfb-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (ruby=2.6.2, postgresql=11, active_record=~> 6.0.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, GabrielBB/xvfb-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/