Skip to content
Shared cli/server fortio workflows

fix error reporting of timeout when getting invalid response, switch build to go 1.22.2 #18

Sign in to view logs

fix error reporting of timeout when getting invalid response, switch build to go 1.22.2

fix error reporting of timeout when getting invalid response, switch build to go 1.22.2 #18

Triggered via pull request April 3, 2024 19:04
@ldemaillyldemailly
opened #914
bad_server
Status Failure
Total duration 3m 11s
Artifacts –

include.yml

on: pull_request
call-gochecks  /  check
3m 2s
call-gochecks / check
call-codecov  /  coverage
1m 50s
call-codecov / coverage
Matrix: call-codeql / Analyze
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
call-gochecks / check: fhttp/http_client.go#L1092
type assertion on error will fail on wrapped errors. Use errors.As to check for specific errors (errorlint)
call-gochecks / check
issues found
call-codecov / coverage
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: codecov/codecov-action@ab904c41d6ece82784817410c45d8b8c02684457. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.