Skip to content

release 9.0.13 #2660

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.

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

Merged
merged 2 commits into from
Jul 17, 2025
Merged

release 9.0.13 #2660

merged 2 commits into from
Jul 17, 2025

Conversation

Kerkesni
Copy link
Contributor

Issue: BB-700

@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Hello kerkesni,

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 Jul 17, 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.

@Kerkesni
Copy link
Contributor Author

/approve

@scality scality deleted a comment from bert-e Jul 17, 2025
@scality scality deleted a comment from bert-e Jul 17, 2025
@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Waiting for approval

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

  • the author

  • 2 peers

The following options are set: approve

Copy link

codecov bot commented Jul 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.34%. Comparing base (2505480) to head (2abfc06).
Report is 2 commits behind head on development/9.0.

Additional details and impacted files

Impacted file tree graph

see 1 file with indirect coverage changes

Components Coverage Δ
Bucket Notification 75.47% <ø> (ø)
Core Library 79.69% <ø> (ø)
Ingestion 70.14% <ø> (-0.09%) ⬇️
Lifecycle 77.94% <ø> (ø)
Oplog Populator 85.06% <ø> (ø)
Replication 58.55% <ø> (ø)
Bucket Scanner 85.60% <ø> (ø)
@@                 Coverage Diff                 @@
##           development/9.0    #2660      +/-   ##
===================================================
- Coverage            73.35%   73.34%   -0.01%     
===================================================
  Files                  201      201              
  Lines                13387    13387              
===================================================
- Hits                  9820     9819       -1     
- Misses                3557     3558       +1     
  Partials                10       10              
Flag Coverage Δ
api:retry 9.47% <ø> (ø)
api:routes 9.28% <ø> (ø)
bucket-scanner 85.60% <ø> (ø)
ft_test:queuepopulator 8.91% <ø> (ø)
ingestion 12.54% <ø> (-0.01%) ⬇️
lib 7.38% <ø> (ø)
lifecycle 18.77% <ø> (ø)
notification 1.05% <ø> (ø)
replication 18.53% <ø> (ø)
unit 48.98% <ø> (ø)

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Build failed

The build for commit did not succeed in branch improvement/BB-700

The following options are set: approve

Kerkesni added 2 commits July 17, 2025 14:28
Debian Buster repositories are no longer available.
Debian Buster reached end-of-life and has been moved to archive repositories

Issue: BB-697
@Kerkesni Kerkesni force-pushed the improvement/BB-700 branch from 23b10bf to 2abfc06 Compare July 17, 2025 12:29
@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

History mismatch

Merge commit #23b10bf6dc7d7e6f3a252e13869a4b62d9467131 on the integration branch
w/9.1/improvement/BB-700 is merging a branch which is neither the current
branch improvement/BB-700 nor the development branch
development/9.1.

It is likely due to a rebase of the branch improvement/BB-700 and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

The following options are set: approve

@Kerkesni
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve

@scality scality deleted a comment from bert-e Jul 17, 2025
@bert-e
Copy link
Contributor

bert-e commented Jul 17, 2025

Build failed

The build for commit did not succeed in branch improvement/BB-700

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jul 17, 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.6

Please check the status of the associated issue BB-700.

Goodbye kerkesni.

The following options are set: approve

@bert-e bert-e merged commit 2abfc06 into development/9.0 Jul 17, 2025
13 of 14 checks passed
@bert-e bert-e deleted the improvement/BB-700 branch July 17, 2025 13:08
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