Skip to content

fix: use require.NoError instead of t.Fatal(err) in client package #15510

fix: use require.NoError instead of t.Fatal(err) in client package

fix: use require.NoError instead of t.Fatal(err) in client package #15510

Triggered via pull request October 9, 2024 05:56
Status Failure
Total duration 18m 25s
Artifacts 4

tests.yaml

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

Annotations

1 error and 2 warnings
arm64 / test (linux-arm64-integration-1-cpu)
Process completed with exit code 2.
arm64 / test (linux-386-unit-1-cpu)
No files were found with the provided path: ./**/junit_*.xml. No artifacts will be uploaded.
arm64 / test (linux-arm64-integration-1-cpu)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.319.1. Please update to the latest version 2.320.0

Artifacts

Produced during runtime
Name Size
linux-arm64-integration-1-cpu
133 KB
linux-arm64-integration-2-cpu
10.8 KB
linux-arm64-integration-4-cpu
10.8 KB
linux-arm64-unit-4-cpu
41.6 KB