Skip to content

CLDSRV-835: Retry flaky upload socket hang up#6118

Open
BourgoisMickael wants to merge 1 commit intodevelopment/9.3from
bugfix/CLDSRV-835-socket-hang-up
Open

CLDSRV-835: Retry flaky upload socket hang up#6118
BourgoisMickael wants to merge 1 commit intodevelopment/9.3from
bugfix/CLDSRV-835-socket-hang-up

Conversation

@BourgoisMickael
Copy link
Contributor

  1) DELETE object
       With default signature
         with multipart upload
           "before all" hook for "should delete a object uploaded in parts successfully":
     TimeoutError: socket hang up

```
  1) DELETE object
       With default signature
         with multipart upload
           "before all" hook for "should delete a object uploaded in parts successfully":
     TimeoutError: socket hang up
```
@bert-e
Copy link
Contributor

bert-e commented Mar 18, 2026

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 Mar 18, 2026

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.

@BourgoisMickael BourgoisMickael requested review from a team, fredmnl, jonathan-gramain and tcarmet and removed request for a team March 18, 2026 23:55
@BourgoisMickael
Copy link
Contributor Author

/create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Mar 18, 2026

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
  • development/9.0
  • development/9.1
  • development/9.2

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: create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Mar 18, 2026

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

@claude
Copy link

claude bot commented Mar 18, 2026

LGTM

Review by Claude Code

@codecov
Copy link

codecov bot commented Mar 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.23%. Comparing base (b045823) to head (9d7619f).
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph
see 1 file with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.3    #6118      +/-   ##
===================================================
- Coverage            84.24%   84.23%   -0.01%     
===================================================
  Files                  206      206              
  Lines                13251    13251              
===================================================
- Hits                 11163    11162       -1     
- Misses                2088     2089       +1     
Flag Coverage Δ
file-ft-tests 67.90% <ø> (ø)
kmip-ft-tests 28.08% <ø> (ø)
mongo-v0-ft-tests 69.08% <ø> (-0.03%) ⬇️
mongo-v1-ft-tests 69.12% <ø> (+<0.01%) ⬆️
multiple-backend 36.30% <ø> (ø)
sur-tests 35.63% <ø> (ø)
sur-tests-inflights 37.49% <ø> (ø)
unit 69.90% <ø> (ø)
utapi-v2-tests 34.36% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants