Skip to content
Shared library fortio workflows

Fix the tight loop of empty Read() bug. Differentiate the type of interrupt errors #59

Sign in to view logs

Fix the tight loop of empty Read() bug. Differentiate the type of interrupt errors

Fix the tight loop of empty Read() bug. Differentiate the type of interrupt errors #59

Triggered via pull request September 1, 2024 22:47
@ldemaillyldemailly
synchronize #21
differentiate_error
Status Failure
Total duration 3m 4s
Artifacts –

include.yml

on: pull_request
call-codecov  /  coverage
8s
call-codecov / coverage
Matrix: call-codeql / Analyze
Matrix: call-gochecks / check
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 warning
call-gochecks / check (windows-latest): timeoutreader_unix.go#L13
undefined: unix.Timeval
call-gochecks / check (windows-latest): timeoutreader_unix.go#L14
undefined: unix.NsecToTimeval
call-gochecks / check (windows-latest): timeoutreader_unix.go#L18
undefined: unix.Timeval
call-gochecks / check (windows-latest): timeoutreader_unix.go#L19
undefined: unix.FdSet
call-gochecks / check (windows-latest): timeoutreader_unix.go#L21
undefined: unix.Select
call-gochecks / check (windows-latest): timeoutreader_unix.go#L33
undefined: unix.Read
call-gochecks / check (windows-latest)
Process completed with exit code 2.
call-codecov / coverage
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@ab904c41d6ece82784817410c45d8b8c02684457. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/