Skip to content
Turbo CI

fulfill disconnect interface #93

Sign in to view logs

fulfill disconnect interface

fulfill disconnect interface #93

Triggered via pull request June 25, 2024 08:29
@turbocrimeturbocrime
opened #56
turbocrime/use-disconnect
Status Failure
Total duration 46s
Artifacts –

turbo-ci.yml

on: pull_request
Lint
16s
Lint
Build
17s
Build
test
19s
test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
Lint
Process completed with exit code 254.
Build
Process completed with exit code 254.
test
Process completed with exit code 254.
Lint
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.316.1. Please update to the latest version 2.317.0
Lint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: buildjet/cache@v3, pnpm/action-setup@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.316.1. Please update to the latest version 2.317.0
Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: buildjet/cache@v3, pnpm/action-setup@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
test
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.316.1. Please update to the latest version 2.317.0
test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: buildjet/cache@v3, pnpm/action-setup@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.