Skip to content

CLDSRV-741: Test iam action version PutRetention & LegalHold #5956

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Sep 29, 2025
Merged

CLDSRV-741: Test iam action version PutRetention & LegalHold #5956

merged 2 commits into from
Sep 29, 2025

Conversation

@BourgoisMickael
Copy link
Contributor

Related to ARSN-297

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

Hello bourgoismickael,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval ⭐
/bypass_build_status Bypass the build and test status ⭐
/bypass_commit_size Bypass the check on the size of the changeset TBA ⭐
/bypass_incompatible_branch Bypass the check on the source branch prefix ⭐
/bypass_jira_check Bypass the Jira issue check ⭐
/bypass_peer_approval Bypass the pull request peers' approval ⭐
/bypass_leader_approval Bypass the pull request leaders' approval ⭐
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

Copilot AI reviewed Sep 29, 2025
View reviewed changes
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds test coverage for IAM actions related to object retention and legal hold operations with version IDs, specifically testing that the correct action (s3:PutObjectRetention vs s3:PutObjectVersionRetention) is used for these operations.

  • Adds comprehensive test suites to verify IAM action behavior for both retention and legal hold operations
  • Updates the BucketUtility.empty() method to support bypassing governance retention when cleaning up test buckets
  • Tests verify that standard S3 actions work correctly with version IDs (no longer requiring non-standard versioned actions)

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
tests/functional/aws-node-sdk/test/object/putRetention.js Adds IAM action tests for putObjectRetention with and without version IDs
tests/functional/aws-node-sdk/test/object/putObjectLegalHold.js Adds IAM action tests for putObjectLegalHold with and without version IDs
tests/functional/aws-node-sdk/lib/utility/bucket-util.js Updates empty method to support bypassing governance retention for test cleanup

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@codecov
Copy link

codecov bot commented Sep 29, 2025 •
edited
Loading

❌ 37 Tests Failed:

Tests completed Failed Passed Skipped
7849 37 7812 0
View the top 3 failed test(s) by shortest run time 
"after each" hook for "versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws "::AWS backend delete object w. versioning: using bucket location constraint With v4 signature "after each" hook for "versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws "
Stack Traces | 0.001s run time 
done() called multiple times in hook <AWS backend delete object w. versioning: using bucket location constraint With v4 signature "after each" hook for "versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws "> of file .../multipleBackend/delete/deleteAwsVersioning.js; in addition, done() received error: NoSuchBucket: The specified bucket does not exist.
    at Request.extractError (.../lib/services/s3.js:757:35)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (.../aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (.../aws-sdk/lib/request.js:686:14)
    at Request.transition (.../aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (.../aws-sdk/lib/state_machine.js:14:12)
    at .../aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (.../aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (.../aws-sdk/lib/request.js:688:12)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:116:18)
    at Request.emit (.../aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (.../aws-sdk/lib/request.js:686:14)
    at Request.transition (.../aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (.../aws-sdk/lib/state_machine.js:14:12)
    at .../aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (.../aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (.../aws-sdk/lib/request.js:688:12)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:116:18)
    at callNextListener (.../aws-sdk/lib/sequential_executor.js:96:12)
    at IncomingMessage.onEnd (.../aws-sdk/lib/event_listeners.js:417:13)
    at IncomingMessage.emit (node:events:531:35)
    at IncomingMessage.emit (node:domain:489:12)
    at endReadableNT (node:internal/streams/readable:1698:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  code: 'NoSuchBucket',
  region: null,
  time: 2025-09-29T01:03:45.952Z,
  requestId: '4de92b3de248bd8c3fad',
  extendedRequestId: '4de92b3de248bd8c3fad',
  cfId: undefined,
  statusCode: 404,
  retryable: false
}
"after each" hook for "versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws "::AWS backend delete object w. versioning: using bucket location constraint With v4 signature "after each" hook for "versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws "
Stack Traces | 0.001s run time 
Expected success deleting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:03:45.948Z
+ }
- null

"after each" hook for "versioning not configured: if specifying "null" version, should delete specific version in AWS backend"::AWS backend delete multiple objects w. versioning: using object location constraint With default signature "after each" hook for "versioning not configured: if specifying "null" version, should delete specific version in AWS backend"
Stack Traces | 0.002s run time 
Cannot read properties of null (reading 'VersionId')
"after each" hook for "versioning not configured: if specifying "null" version, should delete specific version in AWS backend"::AWS backend delete multiple objects w. versioning: using object location constraint With default signature "after each" hook for "versioning not configured: if specifying "null" version, should delete specific version in AWS backend"
Stack Traces | 0.002s run time 
done() called multiple times in hook <AWS backend delete multiple objects w. versioning: using object location constraint With default signature "after each" hook for "versioning not configured: if specifying "null" version, should delete specific version in AWS backend"> of file .../multipleBackend/delete/deleteAwsVersioning.js
"after each" hook for "versioning not configured: if specifying "null" version, should delete specific version in AWS backend"::AWS backend delete multiple objects w. versioning: using object location constraint With v4 signature "after each" hook for "versioning not configured: if specifying "null" version, should delete specific version in AWS backend"
Stack Traces | 0.003s run time 
Cannot read properties of null (reading 'VersionId')
"after each" hook for "versioning not configured: should put/get a tag set on the latest version if no version is specified"::AWS backend object put/get tagging with versioning With v4 signature "after each" hook for "versioning not configured: should put/get a tag set on the latest version if no version is specified"
Stack Traces | 0.003s run time 
The specified bucket does not exist.
"after each" hook for "should return a LocationNotFound if trying to get a version that was deleted in AWS but exists in s3 metadata"::AWS backend get object with versioning With v4 signature "after each" hook for "should return a LocationNotFound if trying to get a version that was deleted in AWS but exists in s3 metadata"
Stack Traces | 0.004s run time 
done() called multiple times in hook <AWS backend get object with versioning With v4 signature "after each" hook for "should return a LocationNotFound if trying to get a version that was deleted in AWS but exists in s3 metadata"> of file .../multipleBackend/get/getAwsVersioning.js
"after each" hook for "should return a LocationNotFound if trying to get a version that was deleted in AWS but exists in s3 metadata"::AWS backend get object with versioning With v4 signature "after each" hook for "should return a LocationNotFound if trying to get a version that was deleted in AWS but exists in s3 metadata"
Stack Traces | 0.004s run time 
Cannot read properties of null (reading 'VersionId')
"after each" hook for "versioning not configured: should delete a tag set on the latest version if no version is specified"::AWS backend object delete tagging with versioning  With v4 signature "after each" hook for "versioning not configured: should delete a tag set on the latest version if no version is specified"
Stack Traces | 0.004s run time 
The specified bucket does not exist.
"after all" hook for "should delete object from AWS location with bucketMatch set to false"::Multiple backend delete With v4 signature "after all" hook for "should delete object from AWS location with bucketMatch set to false"
Stack Traces | 0.005s run time 
The bucket you tried to delete is not empty.
"after each" hook for "versioning suspended then enabled: should delete a tag set on a specific version (null) if specified"::AWS backend object delete tagging with versioning  With default signature "after each" hook for "versioning suspended then enabled: should delete a tag set on a specific version (null) if specified"
Stack Traces | 0.005s run time 
done() called multiple times in hook <AWS backend object delete tagging with versioning  With default signature "after each" hook for "versioning suspended then enabled: should delete a tag set on a specific version (null) if specified"> of file .../multipleBackend/objectTagging/taggingAwsVersioning-delete.js
"after each" hook for "versioning suspended then enabled: should delete a tag set on a specific version (null) if specified"::AWS backend object delete tagging with versioning  With default signature "after each" hook for "versioning suspended then enabled: should delete a tag set on a specific version (null) if specified"
Stack Traces | 0.005s run time 
Cannot read properties of null (reading 'VersionId')
"after all" hook for "should delete object from AWS location with bucketMatch set to false"::Multiple backend delete With default signature "after all" hook for "should delete object from AWS location with bucketMatch set to false"
Stack Traces | 0.006s run time 
The bucket you tried to delete is not empty.
"after each" hook for "versioning suspended: should create a delete marker in s3 and aws successfully when deleting non-existing object"::AWS backend delete object w. versioning: using bucket location constraint With default signature "after each" hook for "versioning suspended: should create a delete marker in s3 and aws successfully when deleting non-existing object"
Stack Traces | 0.006s run time 
done() called multiple times in hook <AWS backend delete object w. versioning: using bucket location constraint With default signature "after each" hook for "versioning suspended: should create a delete marker in s3 and aws successfully when deleting non-existing object"> of file .../multipleBackend/delete/deleteAwsVersioning.js
"after each" hook for "versioning suspended: should create a delete marker in s3 and aws successfully when deleting non-existing object"::AWS backend delete object w. versioning: using bucket location constraint With default signature "after each" hook for "versioning suspended: should create a delete marker in s3 and aws successfully when deleting non-existing object"
Stack Traces | 0.006s run time 
Expected success deleting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:01:45.939Z
+ }
- null

"after each" hook for "versioning suspended: should put/get a tag set on the latest version if no version is specified"::AWS backend object put/get tagging with versioning With default signature "after each" hook for "versioning suspended: should put/get a tag set on the latest version if no version is specified"
Stack Traces | 0.006s run time 
done() called multiple times in hook <AWS backend object put/get tagging with versioning With default signature "after each" hook for "versioning suspended: should put/get a tag set on the latest version if no version is specified"> of file .../multipleBackend/objectTagging/taggingAwsVersioning-putget.js
"after each" hook for "versioning suspended: should put/get a tag set on the latest version if no version is specified"::AWS backend object put/get tagging with versioning With default signature "after each" hook for "versioning suspended: should put/get a tag set on the latest version if no version is specified"
Stack Traces | 0.006s run time 
Cannot read properties of null (reading 'VersionId')
"after each" hook for "versioning not configured: should put/get acl successfully when versioning not configured"::AWS backend put/get object acl with versioning With v4 signature "after each" hook for "versioning not configured: should put/get acl successfully when versioning not configured"
Stack Traces | 0.009s run time 
done() called multiple times in hook <AWS backend put/get object acl with versioning With v4 signature "after each" hook for "versioning not configured: should put/get acl successfully when versioning not configured"> of file .../multipleBackend/acl/aclAwsVersioning.js
"after each" hook for "versioning not configured: should put/get acl successfully when versioning not configured"::AWS backend put/get object acl with versioning With v4 signature "after each" hook for "versioning not configured: should put/get acl successfully when versioning not configured"
Stack Traces | 0.009s run time 
Cannot read properties of null (reading 'VersionId')
"after each" hook for "should overwrite existing null version if putting object after suspending versioning"::AWS backend get object with versioning With default signature "after each" hook for "should overwrite existing null version if putting object after suspending versioning"
Stack Traces | 0.01s run time 
done() called multiple times in hook <AWS backend get object with versioning With default signature "after each" hook for "should overwrite existing null version if putting object after suspending versioning"> of file .../multipleBackend/get/getAwsVersioning.js; in addition, done() received error: Error [InternalError]: We encountered an internal error. Please try again.
    at Request.extractError (.../lib/services/s3.js:757:35)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (.../aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (.../aws-sdk/lib/request.js:686:14)
    at Request.transition (.../aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (.../aws-sdk/lib/state_machine.js:14:12)
    at .../aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (.../aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (.../aws-sdk/lib/request.js:688:12)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:116:18)
    at Request.emit (.../aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (.../aws-sdk/lib/request.js:686:14)
    at Request.transition (.../aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (.../aws-sdk/lib/state_machine.js:14:12)
    at .../aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (.../aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (.../aws-sdk/lib/request.js:688:12)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:116:18)
    at callNextListener (.../aws-sdk/lib/sequential_executor.js:96:12)
    at IncomingMessage.onEnd (.../aws-sdk/lib/event_listeners.js:417:13)
    at IncomingMessage.emit (node:events:531:35)
    at IncomingMessage.emit (node:domain:489:12)
    at endReadableNT (node:internal/streams/readable:1698:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  code: 'InternalError',
  region: null,
  time: 2025-09-29T01:13:46.049Z,
  requestId: 'be69937b5e4c9158b71b',
  extendedRequestId: 'be69937b5e4c9158b71b',
  cfId: undefined,
  statusCode: 500,
  retryable: true
}
"after each" hook for "should overwrite existing null version if putting object after suspending versioning"::AWS backend get object with versioning With default signature "after each" hook for "should overwrite existing null version if putting object after suspending versioning"
Stack Traces | 0.01s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'us-east-1',
+   retryable: true,
+   time: 2025-09-29T01:13:46.041Z
+ }
- null

should not corrupt object if overwriting an existing part by copying a part while the MPU is being completed::Object Part Copy With v4 signature When copy source was put by MPU should not corrupt object if overwriting an existing part by copying a part while the MPU is being completed
Stack Traces | 0.029s run time 
We encountered an internal error. Please try again.
should not corrupt object if overwriting an existing part by copying a part while the MPU is being completed::Object Part Copy With default signature When copy source was put by MPU should not corrupt object if overwriting an existing part by copying a part while the MPU is being completed
Stack Traces | 0.033s run time 
We encountered an internal error. Please try again.
"after all" hook for "should intiate, put parts and complete mpu with 10000 parts"::large mpu "after all" hook for "should intiate, put parts and complete mpu with 10000 parts"
Stack Traces | 6.17s run time 
done() called multiple times in hook <large mpu "after all" hook for "should intiate, put parts and complete mpu with 10000 parts"> of file .../test/object/bigMpu.js
"after all" hook for "should intiate, put parts and complete mpu with 10000 parts"::large mpu "after all" hook for "should intiate, put parts and complete mpu with 10000 parts"
Stack Traces | 6.17s run time 
Unknown encoding: Error [InternalError]: We encountered an internal error. Please try again.
    at Request.extractError (.../lib/services/s3.js:757:35)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (.../aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (.../aws-sdk/lib/request.js:686:14)
    at Request.transition (.../aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (.../aws-sdk/lib/state_machine.js:14:12)
    at .../aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (.../aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (.../aws-sdk/lib/request.js:688:12)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:116:18)
    at Request.emit (.../aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (.../aws-sdk/lib/request.js:686:14)
    at Request.transition (.../aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (.../aws-sdk/lib/state_machine.js:14:12)
    at .../aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (.../aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (.../aws-sdk/lib/request.js:688:12)
    at Request.callListeners (.../aws-sdk/lib/sequential_executor.js:116:18)
    at callNextListener (.../aws-sdk/lib/sequential_executor.js:96:12)
    at IncomingMessage.onEnd (.../aws-sdk/lib/event_listeners.js:417:13)
    at IncomingMessage.emit (node:events:531:35)
    at IncomingMessage.emit (node:domain:489:12)
    at endReadableNT (node:internal/streams/readable:1698:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  code: 'InternalError',
  region: null,
  time: 2025-09-29T02:36:44.742Z,
  requestId: 'dd5dc1f8b6429d665615',
  extendedRequestId: 'dd5dc1f8b6429d665615',
  cfId: undefined,
  statusCode: 500,
  retryable: true
}
"before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: true "::Multiple backend get object With v4 signature Complete MPU then get object on AWS location with bucketMatch: true  "before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: true "
Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'UploadId')
"before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: true "::Multiple backend get object With default signature Complete MPU then get object on AWS location with bucketMatch: true  "before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: true "
Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
"before all" hook for "should get an object from mem"::Multiple backend get object With default signature with objects in all available backends (mem/file/AWS) "before all" hook for "should get an object from mem"
Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
"before all" hook for "should get an object from mem"::Multiple backend get object With v4 signature with objects in all available backends (mem/file/AWS) "before all" hook for "should get an object from mem"
Stack Traces | 30s run time 
done() called multiple times in hook <Multiple backend get object With v4 signature with objects in all available backends (mem/file/AWS) "before all" hook for "should get an object from mem"> of file .../multipleBackend/acl/aclAwsVersioning.js; in addition, done() received error: Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
    at Socket._onTimeout (node:net:604:8)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7) {
  code: 'TimeoutError',
  time: 2025-09-29T01:12:46.017Z,
  region: 'us-east-1',
  hostname: '127.0.0.1',
  retryable: true
}
"before all" hook for "should get an object from mem"::Multiple backend get object With v4 signature with objects in all available backends (mem/file/AWS) "before all" hook for "should get an object from mem"
Stack Traces | 30s run time 
Err putting object: TimeoutError: Connection timed out after 120000ms
"before each" hook for "should get an object from AWS"::Multiple backend get object With default signature with bucketMatch set to false "before each" hook for "should get an object from AWS"
Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
"before each" hook for "should get an object from AWS"::Multiple backend get object With v4 signature with bucketMatch set to false "before each" hook for "should get an object from AWS"
Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
"before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: false "::Multiple backend get object With default signature Complete MPU then get object on AWS location with bucketMatch: false  "before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: false "
Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
"before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: false "::Multiple backend get object With v4 signature Complete MPU then get object on AWS location with bucketMatch: false  "before each" hook: beforeEachFn for "should get object from MPU on AWS location with bucketMatch: false "
Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
"before all" hook for "should delete object from mem"::Multiple backend delete With v4 signature "before all" hook for "should delete object from mem"
Stack Traces | 30s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T00:29:15.382Z
+ }
- null

"before all" hook for "should delete object from mem"::Multiple backend delete With v4 signature "before all" hook for "should delete object from mem"
Stack Traces | 30s run time 
done() called multiple times in hook <Multiple backend delete With v4 signature "before all" hook for "should delete object from mem"> of file .../multipleBackend/delete/delete.js; in addition, done() received error: Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
    at Socket._onTimeout (node:net:604:8)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7) {
  code: 'TimeoutError',
  time: 2025-09-29T00:30:45.375Z,
  region: 'us-east-1',
  hostname: '127.0.0.1',
  retryable: true
}
"before all" hook for "should delete object from mem"::Multiple backend delete With default signature "before all" hook for "should delete object from mem"
Stack Traces | 30s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T00:28:45.348Z
+ }
- null

"after each" hook for "should put only metadata to mem with mdonly header"::MultipleBackend put object With v4 signature "after each" hook for "should put only metadata to mem with mdonly header"
Stack Traces | 120s run time 
Connection timed out after 120000ms
"after each" hook for "should put only metadata to mem with mdonly header"::MultipleBackend put object With default signature "after each" hook for "should put only metadata to mem with mdonly header"
Stack Traces | 120s run time 
Connection timed out after 120000ms
View the full list of 149 ❄️ flaky test(s) 
multiple delete markers: should be able to get pre-existing versions after creating and deleting several delete markers::AWS backend delete object w. versioning: using object location constraint With default signature multiple delete markers: should be able to get pre-existing versions after creating and deleting several delete markers

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
multiple delete markers: should be able to get pre-existing versions after creating and deleting several delete markers::AWS backend delete object w. versioning: using object location constraint With v4 signature multiple delete markers: should be able to get pre-existing versions after creating and deleting several delete markers

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
multiple delete markers: should get NoSuchObject if only one of the delete markers is deleted::AWS backend delete object w. versioning: using object location constraint With default signature multiple delete markers: should get NoSuchObject if only one of the delete markers is deleted

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
multiple delete markers: should get NoSuchObject if only one of the delete markers is deleted::AWS backend delete object w. versioning: using object location constraint With v4 signature multiple delete markers: should get NoSuchObject if only one of the delete markers is deleted

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
should copy a 0-byte object from mem to AWS::MultipleBackend object copy: AWS With default signature should copy a 0-byte object from mem to AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 19.1s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy a 0-byte object from mem to AWS::MultipleBackend object copy: AWS With v4 signature should copy a 0-byte object from mem to AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.9s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy a 0-byte object on AWS::MultipleBackend object copy: AWS With default signature should copy a 0-byte object on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.8s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy a 0-byte object on AWS::MultipleBackend object copy: AWS With v4 signature should copy a 0-byte object on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.8s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an empty version from scality-internal-file to bucket on AWS backend with versioning with REPLACE directive::AWS backend object copy with versioning With default signature should copy an empty version from scality-internal-file to bucket on AWS backend with versioning with REPLACE directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an empty version from scality-internal-file to bucket on AWS backend with versioning with REPLACE directive::AWS backend object copy with versioning With v4 signature should copy an empty version from scality-internal-file to bucket on AWS backend with versioning with REPLACE directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.4s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:39:58.081Z
+ }
- null

should copy an empty version from scality-internal-mem to bucket on AWS backend with versioning with REPLACE directive::AWS backend object copy with versioning With default signature should copy an empty version from scality-internal-mem to bucket on AWS backend with versioning with REPLACE directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.4s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an empty version from scality-internal-mem to bucket on AWS backend with versioning with REPLACE directive::AWS backend object copy with versioning With v4 signature should copy an empty version from scality-internal-mem to bucket on AWS backend with versioning with REPLACE directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.1s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:39:17.013Z
+ }
- null

should copy an object from AWS to mem relying on destination bucket location::MultipleBackend object copy: AWS With default signature should copy an object from AWS to mem relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.8s run time 
err creating mpu: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:24:46.238Z
+ }
- null

should copy an object from AWS to mem relying on destination bucket location::MultipleBackend object copy: AWS With v4 signature should copy an object from AWS to mem relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.8s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object from AWS to mem with "COPY" directive and aws location metadata::MultipleBackend object copy: AWS With default signature should copy an object from AWS to mem with "COPY" directive and aws location metadata

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 19.1s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object from AWS to mem with "COPY" directive and aws location metadata::MultipleBackend object copy: AWS With v4 signature should copy an object from AWS to mem with "COPY" directive and aws location metadata

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.9s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object from AWS to mem with encryption with REPLACE directive but no location constraint::MultipleBackend object copy: AWS With default signature should copy an object from AWS to mem with encryption with REPLACE directive but no location constraint

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.2s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object from AWS to mem with encryption with REPLACE directive but no location constraint::MultipleBackend object copy: AWS With v4 signature should copy an object from AWS to mem with encryption with REPLACE directive but no location constraint

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.6s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object from Azure to AWS relying on destination bucket location::MultipleBackend object copy: AWS With default signature should copy an object from Azure to AWS relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.4s run time 
Expected values to be strictly equal:
+ actual - expected

+ 'TimeoutError'
- 'NoSuchKey'

should copy an object from Azure to AWS relying on destination bucket location::MultipleBackend object copy: AWS With v4 signature should copy an object from Azure to AWS relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.4s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object from mem to AWS relying on destination bucket location::MultipleBackend object copy: AWS With default signature should copy an object from mem to AWS relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
should copy an object from mem to AWS relying on destination bucket location::MultipleBackend object copy: AWS With v4 signature should copy an object from mem to AWS relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.2s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object from mem to AWS with encryption with REPLACE directive but no location constraint::MultipleBackend object copy: AWS With default signature should copy an object from mem to AWS with encryption with REPLACE directive but no location constraint

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.4s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object from mem to AWS with encryption with REPLACE directive but no location constraint::MultipleBackend object copy: AWS With v4 signature should copy an object from mem to AWS with encryption with REPLACE directive but no location constraint

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.3s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object from mem to AWS::MultipleBackend object copy: AWS With default signature should copy an object from mem to AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object from mem to AWS::MultipleBackend object copy: AWS With v4 signature should copy an object from mem to AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS location with bucketMatch equals false to a different AWS location with bucketMatch equals true::MultipleBackend object copy: AWS With default signature should copy an object on AWS location with bucketMatch equals false to a different AWS location with bucketMatch equals true

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS location with bucketMatch equals false to a different AWS location with bucketMatch equals true::MultipleBackend object copy: AWS With v4 signature should copy an object on AWS location with bucketMatch equals false to a different AWS location with bucketMatch equals true

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS to a different AWS location with source object READ access::MultipleBackend object copy: AWS With default signature should copy an object on AWS to a different AWS location with source object READ access

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.2s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS to a different AWS location with source object READ access::MultipleBackend object copy: AWS With v4 signature should copy an object on AWS to a different AWS location with source object READ access

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.5s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS with REPLACE::MultipleBackend object copy: AWS With default signature should copy an object on AWS with REPLACE

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.4s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS with REPLACE::MultipleBackend object copy: AWS With v4 signature should copy an object on AWS with REPLACE

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.3s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS::MultipleBackend object copy: AWS With default signature should copy an object on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.8s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object on AWS::MultipleBackend object copy: AWS With v4 signature should copy an object on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.8s run time 
Expected success but got error: TimeoutError: Connection timed out after 120000ms
should copy an object without location contraint from mem to AWS relying on destination bucket location::MultipleBackend object copy: AWS With default signature should copy an object without location contraint from mem to AWS relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 19.1s run time 
err creating mpu: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:24:16.297Z
+ }
- null

should copy an object without location contraint from mem to AWS relying on destination bucket location::MultipleBackend object copy: AWS With v4 signature should copy an object without location contraint from mem to AWS relying on destination bucket location

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.9s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy empty object from scality-internal-file to bucket on AWS backend with versioning with REPLACE::AWS backend object copy with versioning With default signature should copy empty object from scality-internal-file to bucket on AWS backend with versioning with REPLACE

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.9s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy empty object from scality-internal-file to bucket on AWS backend with versioning with REPLACE::AWS backend object copy with versioning With v4 signature should copy empty object from scality-internal-file to bucket on AWS backend with versioning with REPLACE

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.6s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:39:47.659Z
+ }
- null

should copy empty object from scality-internal-mem to bucket on AWS backend with versioning with REPLACE::AWS backend object copy with versioning With default signature should copy empty object from scality-internal-mem to bucket on AWS backend with versioning with REPLACE

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.6s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should copy empty object from scality-internal-mem to bucket on AWS backend with versioning with REPLACE::AWS backend object copy with versioning With v4 signature should copy empty object from scality-internal-mem to bucket on AWS backend with versioning with REPLACE

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:38:46.881Z
+ }
- null

should copy object from scality-internal-file to bucket on AWS backend with versioning with COPY::AWS backend object copy with versioning With default signature should copy object from scality-internal-file to bucket on AWS backend with versioning with COPY

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 10.4s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:37:58.001Z
+ }
- null

should copy object from scality-internal-file to bucket on AWS backend with versioning with COPY::AWS backend object copy with versioning With v4 signature should copy object from scality-internal-file to bucket on AWS backend with versioning with COPY

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.1s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:41:17.092Z
+ }
- null

should copy object from scality-internal-mem to bucket on AWS backend with versioning with COPY::AWS backend object copy with versioning With default signature should copy object from scality-internal-mem to bucket on AWS backend with versioning with COPY

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.1s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:37:16.945Z
+ }
- null

should copy object from scality-internal-mem to bucket on AWS backend with versioning with COPY::AWS backend object copy with versioning With v4 signature should copy object from scality-internal-mem to bucket on AWS backend with versioning with COPY

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.9s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:40:17.031Z
+ }
- null

should copy version from scality-internal-file to bucket on AWS backend with versioning with COPY directive::AWS backend object copy with versioning With default signature should copy version from scality-internal-file to bucket on AWS backend with versioning with COPY directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.9s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:38:16.954Z
+ }
- null

should copy version from scality-internal-file to bucket on AWS backend with versioning with COPY directive::AWS backend object copy with versioning With v4 signature should copy version from scality-internal-file to bucket on AWS backend with versioning with COPY directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.6s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:41:47.738Z
+ }
- null

should copy version from scality-internal-mem to bucket on AWS backend with versioning with COPY directive::AWS backend object copy with versioning With default signature should copy version from scality-internal-mem to bucket on AWS backend with versioning with COPY directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.6s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:37:47.586Z
+ }
- null

should copy version from scality-internal-mem to bucket on AWS backend with versioning with COPY directive::AWS backend object copy with versioning With v4 signature should copy version from scality-internal-mem to bucket on AWS backend with versioning with COPY directive

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:40:46.962Z
+ }
- null

should delete tags from object on awsbackend backend::Object tagging with multiple backends With default signature deleteObjectTagging should delete tags from object on awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.1s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should delete tags from object on awsbackend backend::Object tagging with multiple backends With v4 signature deleteObjectTagging should delete tags from object on awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 9.91s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should delete the correct version even if other versions or delete markers put directly on aws::AWS backend delete object w. versioning: using object location constraint With default signature should delete the correct version even if other versions or delete markers put directly on aws

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90s run time 
Cannot read properties of null (reading 'VersionId')
should delete the correct version even if other versions or delete markers put directly on aws::AWS backend delete object w. versioning: using object location constraint With v4 signature should delete the correct version even if other versions or delete markers put directly on aws

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
should get correct data from aws backend using version IDs after putting null versions, putting versions, putting more null versions and then putting more versions::AWS backend get object with versioning With v4 signature should get correct data from aws backend using version IDs after putting null versions, putting versions, putting more null versions and then putting more versions

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should get correct data from aws backend using version IDs::AWS backend get object with versioning With v4 signature should get correct data from aws backend using version IDs

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should get correct version when getting without version ID::AWS backend get object with versioning With v4 signature should get correct version when getting without version ID

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
should get tags from object on awsbackend backend::Object tagging with multiple backends With default signature getObjectTagging should get tags from object on awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should get tags from object on awsbackend backend::Object tagging with multiple backends With v4 signature getObjectTagging should get tags from object on awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 31.2s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should get the body of part 5 when ordered MPU::GET object With default signature With PartNumber field should get the body of part 5 when ordered MPU

Flake rate in main: 21.86% (Passed 193 times, Failed 54 times)

Stack Traces | 0.106s run time 
Expected success, got error TimeoutError: Connection timed out after 120000ms
should get the new latest version after deleting the latestspecific version::AWS backend delete object w. versioning: using object location constraint With default signature should get the new latest version after deleting the latestspecific version

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
should get the new latest version after deleting the latestspecific version::AWS backend delete object w. versioning: using object location constraint With v4 signature should get the new latest version after deleting the latestspecific version

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
should intiate, put parts and complete mpu with 10000 parts::large mpu should intiate, put parts and complete mpu with 10000 parts

Flake rate in main: 21.86% (Passed 193 times, Failed 54 times)

Stack Traces | 38s run time 
Expected success, got error TimeoutError: Connection timed out after 120000ms
should not return an error deleting a version that was already deleted directly from AWS backend::AWS backend delete object w. versioning: using object location constraint With default signature should not return an error deleting a version that was already deleted directly from AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
should not return an error deleting a version that was already deleted directly from AWS backend::AWS backend delete object w. versioning: using object location constraint With v4 signature should not return an error deleting a version that was already deleted directly from AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
should not return error on deleting tags from object that has had delete markers put directly on AWS::Object tagging with multiple backends With default signature deleteObjectTagging should not return error on deleting tags from object that has had delete markers put directly on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.8s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should not return error on deleting tags from object that has had delete markers put directly on AWS::Object tagging with multiple backends With v4 signature deleteObjectTagging should not return error on deleting tags from object that has had delete markers put directly on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should not return error on getting tags from object that has had a delete marker put directly on AWS::Object tagging with multiple backends With default signature getObjectTagging should not return error on getting tags from object that has had a delete marker put directly on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 9.8s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should not return error on getting tags from object that has had a delete marker put directly on AWS::Object tagging with multiple backends With v4 signature getObjectTagging should not return error on getting tags from object that has had a delete marker put directly on AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.4s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should not return error putting tags to correct object version in AWS, even if a delete marker was created directly on AWS before tags are put::Object tagging with multiple backends With default signature putObject with tags and putObjectTagging should not return error putting tags to correct object version in AWS, even if a delete marker was created directly on AWS before tags are put

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 31.1s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should not return error putting tags to correct object version in AWS, even if a delete marker was created directly on AWS before tags are put::Object tagging with multiple backends With v4 signature putObject with tags and putObjectTagging should not return error putting tags to correct object version in AWS, even if a delete marker was created directly on AWS before tags are put

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 19.2s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should not return version ids when versioning has not been configured via CloudServer, even when version id specified::AWS backend get object with versioning With default signature should not return version ids when versioning has not been configured via CloudServer, even when version id specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'UploadId')
should not return version ids when versioning has not been configured via CloudServer, even when version id specified::AWS backend get object with versioning With v4 signature should not return version ids when versioning has not been configured via CloudServer, even when version id specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should not return version ids when versioning has not been configured via CloudServer::AWS backend get object with versioning With default signature should not return version ids when versioning has not been configured via CloudServer

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 0.015s run time 
Cannot read properties of null (reading 'UploadId')
should not return version ids when versioning has not been configured via CloudServer::AWS backend get object with versioning With v4 signature should not return version ids when versioning has not been configured via CloudServer

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 0.04s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'us-east-1',
+   retryable: true,
+   time: 2025-09-29T01:13:46.089Z
+ }
- null

should overwrite existing null version if putting object after suspending versioning::AWS backend get object with versioning With default signature should overwrite existing null version if putting object after suspending versioning

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should overwrite existing null version if putting object after suspending versioning::AWS backend get object with versioning With v4 signature should overwrite existing null version if putting object after suspending versioning

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'us-east-1',
+   retryable: true,
+   time: 2025-09-29T01:15:46.051Z
+ }
- null

should overwrite null version if putting object when versioning is suspended after versioning enabled::AWS backend get object with versioning With v4 signature should overwrite null version if putting object when versioning is suspended after versioning enabled

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 0.044s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'us-east-1',
+   retryable: true,
+   time: 2025-09-29T01:15:46.124Z
+ }
- null

should overwrite the null version if putting object twice before versioning is configured::AWS backend get object with versioning With default signature should overwrite the null version if putting object twice before versioning is configured

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Err putting object: TimeoutError: Connection timed out after 120000ms
should overwrite the null version if putting object twice before versioning is configured::AWS backend get object with versioning With v4 signature should overwrite the null version if putting object twice before versioning is configured

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should put a 0 byte object with tags to awsbackend backend::Object tagging with multiple backends With default signature putObject with tags and putObjectTagging should put a 0 byte object with tags to awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 9.9s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should put a 0 byte object with tags to awsbackend backend::Object tagging with multiple backends With v4 signature putObject with tags and putObjectTagging should put a 0 byte object with tags to awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.5s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should put an object to AWS with no location header::MultipleBackend put object based on bucket location With default signature should put an object to AWS with no location header

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 40s run time 
Timeout of 40000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/put/put.js)
should put an object to AWS with no location header::MultipleBackend put object based on bucket location With v4 signature should put an object to AWS with no location header

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 40s run time 
Timeout of 40000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/put/put.js)
should put an object to mem with no location header::MultipleBackend put object based on bucket location With default signature should put an object to mem with no location header

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 0.004s run time 
Error creating bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
should put an object with tags to awsbackend backend::Object tagging with multiple backends With default signature putObject with tags and putObjectTagging should put an object with tags to awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Error copying object to destination: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:42:47.045Z
+ }
- null

should put an object with tags to awsbackend backend::Object tagging with multiple backends With v4 signature putObject with tags and putObjectTagging should put an object with tags to awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 31.2s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should put tags to preexisting 0 byte object in awsbackend backend::Object tagging with multiple backends With default signature putObject with tags and putObjectTagging should put tags to preexisting 0 byte object in awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 18.9s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should put tags to preexisting 0 byte object in awsbackend backend::Object tagging with multiple backends With v4 signature putObject with tags and putObjectTagging should put tags to preexisting 0 byte object in awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.1s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should put tags to preexisting object in awsbackend backend::Object tagging with multiple backends With default signature putObject with tags and putObjectTagging should put tags to preexisting object in awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.1s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should put tags to preexisting object in awsbackend backend::Object tagging with multiple backends With v4 signature putObject with tags and putObjectTagging should put tags to preexisting object in awsbackend backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 9.91s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
should return a LocationNotFound if trying to get a version that was deleted in AWS but exists in s3 metadata::AWS backend get object with versioning With v4 signature should return a LocationNotFound if trying to get a version that was deleted in AWS but exists in s3 metadata

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should return a LocationNotFound if trying to get an object that was deleted in AWS but exists in s3 metadata::AWS backend get object with versioning With v4 signature should return a LocationNotFound if trying to get an object that was deleted in AWS but exists in s3 metadata

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
should return error if AWS source object has been deleted::MultipleBackend object copy: AWS With default signature should return error if AWS source object has been deleted

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should return error if AWS source object has been deleted::MultipleBackend object copy: AWS With v4 signature should return error if AWS source object has been deleted

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30.1s run time 
Error putting source object: TimeoutError: Connection timed out after 120000ms
should return the correct data getting versioned object even if object is put directly to AWS (creating new version)::AWS backend get object with versioning With v4 signature should return the correct data getting versioned object even if object is put directly to AWS (creating new version)

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should return the correct data getting versioned object even if object was deleted from AWS (creating a delete marker)::AWS backend get object with versioning With v4 signature should return the correct data getting versioned object even if object was deleted from AWS (creating a delete marker)

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should return version id for null version when versioning has been configured via CloudServer::AWS backend get object with versioning With default signature should return version id for null version when versioning has been configured via CloudServer

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/get/getAwsVersioning.js)
should return version id for null version when versioning has been configured via CloudServer::AWS backend get object with versioning With v4 signature should return version id for null version when versioning has been configured via CloudServer

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled then suspended: should delete a tag set on a specific (non-null) version if specified::AWS backend object delete tagging with versioning  With default signature versioning enabled then suspended: should delete a tag set on a specific (non-null) version if specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 71.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should create a delete marker in s3 and aws successfully when deleting existing object::AWS backend delete object w. versioning: using object location constraint With default signature versioning enabled: should create a delete marker in s3 and aws successfully when deleting existing object

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should create a delete marker in s3 and aws successfully when deleting existing object::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning enabled: should create a delete marker in s3 and aws successfully when deleting existing object

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should delete a delete marker in s3 and aws successfully::AWS backend delete object w. versioning: using object location constraint With default signature versioning enabled: should delete a delete marker in s3 and aws successfully

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should delete a delete marker in s3 and aws successfully::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning enabled: should delete a delete marker in s3 and aws successfully

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should delete a specific version in AWS backend successfully::AWS backend delete object w. versioning: using object location constraint With default signature versioning enabled: should delete a specific version in AWS backend successfully

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should delete a specific version in AWS backend successfully::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning enabled: should delete a specific version in AWS backend successfully

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should delete a tag set on a specific version that is not the latest version::AWS backend object delete tagging with versioning  With default signature versioning enabled: should delete a tag set on a specific version that is not the latest version

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-delete.js)
versioning enabled: should delete a tag set on a specific version::AWS backend object delete tagging with versioning  With default signature versioning enabled: should delete a tag set on a specific version

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-delete.js)
versioning enabled: should delete a tag set on the latest version if no version is specified::AWS backend object delete tagging with versioning  With default signature versioning enabled: should delete a tag set on the latest version if no version is specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 19.3s run time 
Cannot read properties of null (reading 'VersionId')
versioning enabled: should get correct acl using version IDs::AWS backend put/get object acl with versioning With default signature versioning enabled: should get correct acl using version IDs

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
versioning enabled: should get correct acl when getting without version ID::AWS backend put/get object acl with versioning With default signature versioning enabled: should get correct acl when getting without version ID

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T00:27:45.266Z
+ }
- null

versioning enabled: should return version id completing mpu::AWS backend complete mpu with versioning With default signature versioning enabled: should return version id completing mpu

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
err creating mpu: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:21:16.241Z
+ }
- null

versioning enabled: should return version id completing mpu::AWS backend complete mpu with versioning With v4 signature versioning enabled: should return version id completing mpu

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
err creating mpu: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:23:16.273Z
+ }
- null

versioning not configured: deleting existing object should not return version id or x-amz-delete-marker: true but should create a delete marker in aws ::AWS backend delete object w. versioning: using object location constraint With default signature versioning not configured: deleting existing object should not return version id or x-amz-delete-marker: true but should create a delete marker in aws

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: deleting existing object should not return version id or x-amz-delete-marker: true but should create a delete marker in aws ::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning not configured: deleting existing object should not return version id or x-amz-delete-marker: true but should create a delete marker in aws

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws ::AWS backend delete object w. versioning: using bucket location constraint With default signature versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws ::AWS backend delete object w. versioning: using bucket location constraint With v4 signature versioning not configured: deleting non-existing object should not return version id or x-amz-delete-marker: true nor create a delete marker in aws

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/delete/deleteAwsVersioning.js)
versioning not configured: if complete mpu on already-existing object, metadata should be overwritten but data of previous versionin AWS should not be deleted::AWS backend complete mpu with versioning With default signature versioning not configured: if complete mpu on already-existing object, metadata should be overwritten but data of previous versionin AWS should not be deleted

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: if complete mpu on already-existing object, metadata should be overwritten but data of previous versionin AWS should not be deleted::AWS backend complete mpu with versioning With v4 signature versioning not configured: if complete mpu on already-existing object, metadata should be overwritten but data of previous versionin AWS should not be deleted

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
err creating mpu: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:22:16.259Z
+ }
- null

versioning not configured: if specifying "null" version, should delete specific version in AWS backend::AWS backend delete multiple objects w. versioning: using object location constraint With default signature versioning not configured: if specifying "null" version, should delete specific version in AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/delete/deleteAwsVersioning.js)
versioning not configured: if specifying "null" version, should delete specific version in AWS backend::AWS backend delete multiple objects w. versioning: using object location constraint With v4 signature versioning not configured: if specifying "null" version, should delete specific version in AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/delete/deleteAwsVersioning.js)
versioning not configured: if specifying "null" version, should delete specific version in AWS backend::AWS backend delete object w. versioning: using object location constraint With default signature versioning not configured: if specifying "null" version, should delete specific version in AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Expected success putting object, got error TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T00:29:45.311Z
+ }
- null

versioning not configured: if specifying "null" version, should delete specific version in AWS backend::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning not configured: if specifying "null" version, should delete specific version in AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: should delete a tag set on the latest version if no version is specified::AWS backend object delete tagging with versioning  With default signature versioning not configured: should delete a tag set on the latest version if no version is specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 31.2s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
versioning not configured: should delete a tag set on the latest version if no version is specified::AWS backend object delete tagging with versioning  With v4 signature versioning not configured: should delete a tag set on the latest version if no version is specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-delete.js)
versioning not configured: should delete a tag set on the version if specified (null)::AWS backend object delete tagging with versioning  With default signature versioning not configured: should delete a tag set on the version if specified (null)

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 9.91s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
versioning not configured: should not return version id completing mpu::AWS backend complete mpu with versioning With default signature versioning not configured: should not return version id completing mpu

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: should not return version id completing mpu::AWS backend complete mpu with versioning With v4 signature versioning not configured: should not return version id completing mpu

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: should put/get a tag set on a specific version if specified (null)::AWS backend object put/get tagging with versioning With default signature versioning not configured: should put/get a tag set on a specific version if specified (null)

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-putget.js)
versioning not configured: should put/get a tag set on the latest version if no version is specified::AWS backend object put/get tagging with versioning With default signature versioning not configured: should put/get a tag set on the latest version if no version is specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-putget.js)
versioning not configured: should put/get a tag set on the latest version if no version is specified::AWS backend object put/get tagging with versioning With v4 signature versioning not configured: should put/get a tag set on the latest version if no version is specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-putget.js)
versioning not configured: should put/get acl successfully when versioning not configured::AWS backend put/get object acl with versioning With default signature versioning not configured: should put/get acl successfully when versioning not configured

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
versioning not configured: should put/get acl successfully when versioning not configured::AWS backend put/get object acl with versioning With v4 signature versioning not configured: should put/get acl successfully when versioning not configured

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
versioning not configured: specifying any version id other than null should not result in its deletion in AWS backend::AWS backend delete object w. versioning: using object location constraint With default signature versioning not configured: specifying any version id other than null should not result in its deletion in AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning not configured: specifying any version id other than null should not result in its deletion in AWS backend::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning not configured: specifying any version id other than null should not result in its deletion in AWS backend

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended then enabled: should delete a tag set on a specific version (null) if specified::AWS backend object delete tagging with versioning  With default signature versioning suspended then enabled: should delete a tag set on a specific version (null) if specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-delete.js)
versioning suspended then enabled: should put/get acl on null version successfully even when latest version is not null version::AWS backend put/get object acl with versioning With default signature versioning suspended then enabled: should put/get acl on null version successfully even when latest version is not null version

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 30s run time 
Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/acl/aclAwsVersioning.js)
versioning suspended: creating a delete marker will overwrite an existing null version that is not the latest version in s3 metadata, but the data of the first null version will remain in AWS::AWS backend delete object w. versioning: using object location constraint With default signature versioning suspended: creating a delete marker will overwrite an existing null version that is not the latest version in s3 metadata, but the data of the first null version will remain in AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: creating a delete marker will overwrite an existing null version that is not the latest version in s3 metadata, but the data of the first null version will remain in AWS::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning suspended: creating a delete marker will overwrite an existing null version that is not the latest version in s3 metadata, but the data of the first null version will remain in AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: creating a delete marker will overwrite an existing null version that is the latest version in s3 metadata, but the data of the first null version will remain in AWS::AWS backend delete object w. versioning: using object location constraint With default signature versioning suspended: creating a delete marker will overwrite an existing null version that is the latest version in s3 metadata, but the data of the first null version will remain in AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: creating a delete marker will overwrite an existing null version that is the latest version in s3 metadata, but the data of the first null version will remain in AWS::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning suspended: creating a delete marker will overwrite an existing null version that is the latest version in s3 metadata, but the data of the first null version will remain in AWS

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: should create a delete marker in s3 and aws successfully when deleting existing object::AWS backend delete object w. versioning: using object location constraint With default signature versioning suspended: should create a delete marker in s3 and aws successfully when deleting existing object

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: should create a delete marker in s3 and aws successfully when deleting existing object::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning suspended: should create a delete marker in s3 and aws successfully when deleting existing object

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: should create a delete marker in s3 and aws successfully when deleting non-existing object::AWS backend delete object w. versioning: using bucket location constraint With default signature versioning suspended: should create a delete marker in s3 and aws successfully when deleting non-existing object

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/delete/deleteAwsVersioning.js)
versioning suspended: should delete a specific version in AWS backend successfully::AWS backend delete object w. versioning: using object location constraint With default signature versioning suspended: should delete a specific version in AWS backend successfully

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: should delete a specific version in AWS backend successfully::AWS backend delete object w. versioning: using object location constraint With v4 signature versioning suspended: should delete a specific version in AWS backend successfully

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 90.1s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: should delete a tag set on a specific version (null)::AWS backend object delete tagging with versioning  With default signature versioning suspended: should delete a tag set on a specific version (null)

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.6s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
versioning suspended: should delete a tag set on the latest version if no version is specified::AWS backend object delete tagging with versioning  With default signature versioning suspended: should delete a tag set on the latest version if no version is specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 19.3s run time 
Error [TimeoutError]: Connection timed out after 120000ms
    at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
    at Object.onceWrapper (node:events:633:28)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:489:12)
    at Socket.emitRequestTimeout (node:_http_client:863:9)
    at Object.onceWrapper (node:events:633:28)
    at Socket.emit (node:events:531:35)
    at Socket.emit (node:domain:489:12)
   ... == null
versioning suspended: should not return version id completing mpu::AWS backend complete mpu with versioning With default signature versioning suspended: should not return version id completing mpu

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
Cannot read properties of null (reading 'VersionId')
versioning suspended: should not return version id completing mpu::AWS backend complete mpu with versioning With v4 signature versioning suspended: should not return version id completing mpu

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 29.9s run time 
err creating mpu: TimeoutError: Connection timed out after 120000ms
+ actual - expected

+ Error [TimeoutError]: Connection timed out after 120000ms
+     at ClientRequest.<anonymous> (.../lib/http/node.js:87:34)
+     at Object.onceWrapper (node:events:633:28)
+     at ClientRequest.emit (node:events:519:28)
+     at ClientRequest.emit (node:domain:489:12)
+     at Socket.emitRequestTimeout (node:_http_client:863:9)
+     at Object.onceWrapper (node:events:633:28)
+     at Socket.emit (node:events:531:35)
+     at Socket.emit (node:domain:489:12)
+     at Socket._onTimeout (node:net:604:8)
+     at listOnTimeout (node:internal/timers:588:17)
+     at process.processTimers (node:internal/timers:523:7) {
+   code: 'TimeoutError',
+   hostname: '127.0.0.1',
+   region: 'awsbackend',
+   retryable: true,
+   time: 2025-09-29T01:22:46.196Z
+ }
- null

versioning suspended: should put/get a tag set on the latest version if no version is specified::AWS backend object put/get tagging with versioning With default signature versioning suspended: should put/get a tag set on the latest version if no version is specified

Flake rate in main: 70.72% (Passed 65 times, Failed 157 times)

Stack Traces | 120s run time 
Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../multipleBackend/objectTagging/taggingAwsVersioning-putget.js)

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

@BourgoisMickael BourgoisMickael requested review from a team, DarkIsDude, anurag4DSB, dvasilas and williamlardier and removed request for a team September 29, 2025 07:46
@BourgoisMickael BourgoisMickael requested review from a team September 29, 2025 09:17
@BourgoisMickael
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/9.0

  • ✔️ development/9.1

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

Queue build failed

The corresponding build for the queue failed:

  • Checkout the status page.
  • Identify the failing build and review the logs.
  • If no issue is found, re-run the build.
  • If an issue is identified, checkout the steps below to remove
    the pull request from the queue for further analysis and maybe rebase/merge.
Remove the pull request from the queue
  • Add a /wait comment on this pull request.
  • Click on login on the status page.
  • Go into the manage page.
  • Find the option called Rebuild the queue and click on it.
    Bert-E will loop again on all pull requests to put the valid ones
    in the queue again, while skipping the one with the /wait comment.
  • Wait for the new queue to merge, then merge/rebase your pull request
    with the latest changes to then work on a proper fix.
  • Once the issue is fixed, delete the /wait comment and
    follow the usual process to merge the pull request.

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/9.0

  • ✔️ development/9.1

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8

Please check the status of the associated issue CLDSRV-741.

Goodbye bourgoismickael.

@bert-e bert-e merged commit db0280e into development/9.0 Sep 29, 2025
118 of 122 checks passed
@bert-e bert-e deleted the improvement/CLDSRV-741-putversionretention branch September 29, 2025 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@anurag4DSB anurag4DSB anurag4DSB approved these changes

@dvasilas dvasilas dvasilas approved these changes

@williamlardier williamlardier williamlardier approved these changes

@DarkIsDude DarkIsDude Awaiting requested review from DarkIsDude DarkIsDude was automatically assigned from scality/object

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@BourgoisMickael @bert-e @anurag4DSB @dvasilas @williamlardier