Skip to content

Adjust functional tests for bucket cors, to detect NotImplemented response via logError #1232

Adjust functional tests for bucket cors, to detect NotImplemented response via logError

Adjust functional tests for bucket cors, to detect NotImplemented response via logError #1232

Triggered via pull request August 20, 2024 01:11
Status Success
Total duration 2m 11s
Artifacts

go-windows.yml

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

Annotations

4 warnings
Test on Go 1.21.x and windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test on Go 1.21.x and windows-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on Go 1.22.x and windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test on Go 1.22.x and windows-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/