Skip to content
Run tests

Avoid stringer-related deadlocks without adding ISGOMOCK #341

Sign in to view logs

Avoid stringer-related deadlocks without adding ISGOMOCK

Avoid stringer-related deadlocks without adding ISGOMOCK #341

Triggered via pull request September 18, 2024 16:50
@JacobOaksJacobOaks
synchronize #204
JacobOaks:joaks/reflect_gomock_detection
Status Failure
Total duration 37s
Artifacts –

test.yaml

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

Annotations

5 errors and 1 warning
test (1.21.x, ubuntu-latest)
Process completed with exit code 1.
test (1.19.x, ubuntu-latest)
The job was canceled because "_1_21_x_ubuntu-latest" failed.
test (1.19.x, ubuntu-latest)
Process completed with exit code 1.
test (1.22.x, ubuntu-latest)
The job was canceled because "_1_21_x_ubuntu-latest" failed.
test (1.22.x, ubuntu-latest)
The operation was canceled.
test (1.21.x, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/