Skip to content

Conversation

@tmacro
Copy link
Contributor

@tmacro tmacro commented Jan 16, 2026

No description provided.

@codecov
Copy link

codecov bot commented Jan 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.38%. Comparing base (ba82593) to head (297b624).
⚠️ Report is 2 commits behind head on bugfix/CLDSRV-822/fix_multiobject_delete_metric_utapiv1.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph

@@                                   Coverage Diff                                    @@
##           bugfix/CLDSRV-822/fix_multiobject_delete_metric_utapiv1    #6049   +/-   ##
========================================================================================
  Coverage                                                    83.38%   83.38%           
========================================================================================
  Files                                                          189      189           
  Lines                                                        12209    12209           
========================================================================================
  Hits                                                         10181    10181           
  Misses                                                        2028     2028           
Flag Coverage Δ
file-ft-tests 66.78% <ø> (ø)
kmip-ft-tests 26.98% <ø> (ø)
mongo-v0-ft-tests 68.08% <ø> (-0.03%) ⬇️
mongo-v1-ft-tests 68.13% <ø> (+0.02%) ⬆️
multiple-backend 35.67% <ø> (ø)
quota-tests 32.21% <ø> (-0.89%) ⬇️
quota-tests-inflights 34.17% <ø> (-0.04%) ⬇️
unit 67.61% <ø> (ø)
utapi-v2-tests 33.33% <ø> (ø)

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.

Base automatically changed from bugfix/CLDSRV-822/fix_multiobject_delete_metric_utapiv1 to development/9.0 January 16, 2026 23:15
@bert-e
Copy link
Contributor

bert-e commented Jan 16, 2026

Hello tmacro,

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 Jan 16, 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.

@tmacro
Copy link
Contributor Author

tmacro commented Jan 19, 2026

/create_integration_branches

@scality scality deleted a comment from bert-e Jan 19, 2026
@bert-e
Copy link
Contributor

bert-e commented Jan 19, 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

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 Jan 19, 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

@tmacro
Copy link
Contributor Author

tmacro commented Jan 19, 2026

/approve

@bert-e
Copy link
Contributor

bert-e commented Jan 19, 2026

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

  • ✔️ development/9.2

  • ✔️ development/9.3

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

@bert-e
Copy link
Contributor

bert-e commented Jan 19, 2026

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

  • ✔️ development/9.0

  • ✔️ development/9.1

  • ✔️ development/9.2

  • ✔️ development/9.3

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-831.

Goodbye tmacro.

@bert-e bert-e merged commit 06c7fb5 into development/9.0 Jan 19, 2026
26 checks passed
@bert-e bert-e deleted the bugfix/CLDSRV-831/fix_utapiv1_reindex branch January 19, 2026 18:33
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.

6 participants