Skip to content
tests

test: nuts for new commands use their permanent name #1080

Sign in to view logs

test: nuts for new commands use their permanent name

test: nuts for new commands use their permanent name #1080

Triggered via push June 27, 2024 16:09
@mshanemcmshanemc
pushed c9e3356
sm/ga-data-commands
Status Failure
Total duration 14m 27s
Artifacts –

test.yml

on: push
yarn-lockfile-check  /  lockfile-check
7s
yarn-lockfile-check / lockfile-check
linux-unit-tests  /  determine-node-versions
2s
linux-unit-tests / determine-node-versions
Matrix: linux-unit-tests / linux-unit-tests
windows-unit-tests  /  determine-node-versions
1s
windows-unit-tests / determine-node-versions
Matrix: nuts
Matrix: windows-unit-tests / windows-unit-tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
nuts (ubuntu-latest) / yarn test:nuts
Final attempt failed. Child_process exited with error code 14
nuts (windows-latest) / yarn test:nuts
Final attempt failed. Child_process exited with error code 1
nuts (ubuntu-latest) / yarn test:nuts
Attempt 1 failed. Reason: Child_process exited with error code 5
nuts (ubuntu-latest) / yarn test:nuts
Attempt 2 failed. Reason: Child_process exited with error code 14
nuts (windows-latest) / yarn test:nuts
Attempt 1 failed. Reason: Child_process exited with error code 1
nuts (windows-latest) / yarn test:nuts
Attempt 2 failed. Reason: Child_process exited with error code 1