Skip to content
CI

fix: S3 does not throw error if you try to delete a non-existing object #35

Sign in to view logs

fix: S3 does not throw error if you try to delete a non-existing object

fix: S3 does not throw error if you try to delete a non-existing object #35

Triggered via push January 22, 2024 06:39
@james-hujames-hu
pushed 5252070
master
Status Failure
Total duration 29s
Artifacts –

ci.yml

on: push
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 warnings
build-and-test (16.x): src/s3.ts#L3
'PossibleAwsError' is declared but its value is never read.
build-and-test (16.x)
Process completed with exit code 2.
build-and-test (20.x)
The job was canceled because "_16_x" failed.
build-and-test (20.x): src/s3.ts#L3
'PossibleAwsError' is declared but its value is never read.
build-and-test (20.x)
Process completed with exit code 2.
build-and-test (18.x): src/s3.ts#L3
'PossibleAwsError' is declared but its value is never read.
build-and-test (18.x)
The operation was canceled.
build-and-test (16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-test (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-test (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/