Skip to content
Tests

fix: add CLOEXEC flag to socket created directly #598

Sign in to view logs

fix: add CLOEXEC flag to socket created directly

fix: add CLOEXEC flag to socket created directly #598

Triggered via pull request October 1, 2024 12:29
@smirasmira
opened #550
smira:fix/cloexec
Status Success
Total duration 3m 41s
Artifacts –

tests.yml

on: pull_request
Matrix: integration-tests
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
integration-tests (1.20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration-tests (1.21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit-tests (1.20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit-tests (1.21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/