Skip to content

Release 9.0.7#2647

Merged
bert-e merged 1 commit intodevelopment/9.0from
improvement/BB-687
May 19, 2025
Merged

Release 9.0.7#2647
bert-e merged 1 commit intodevelopment/9.0from
improvement/BB-687

Conversation

@francoisferrand
Copy link
Copy Markdown
Contributor

Issue: BB-687

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented May 18, 2025

Hello francoisferrand,

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.

@codecov
Copy link
Copy Markdown

codecov bot commented May 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.11%. Comparing base (096d396) to head (d98bb77).
⚠️ Report is 34 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.37% <ø> (ø)
Core Library 79.69% <ø> (ø)
Ingestion 70.23% <ø> (+0.08%) ⬆️
Lifecycle 76.88% <ø> (ø)
Oplog Populator 85.06% <ø> (ø)
Replication 58.55% <ø> (ø)
Bucket Scanner 85.60% <ø> (ø)
@@               Coverage Diff                @@
##           development/9.0    #2647   +/-   ##
================================================
  Coverage            73.11%   73.11%           
================================================
  Files                  201      201           
  Lines                13385    13385           
================================================
+ Hits                  9786     9787    +1     
+ Misses                3589     3588    -1     
  Partials                10       10           
Flag Coverage Δ
api:retry 9.47% <ø> (ø)
api:routes 9.29% <ø> (ø)
bucket-scanner 85.60% <ø> (ø)
ft_test:queuepopulator 8.91% <ø> (ø)
ingestion 12.55% <ø> (+<0.01%) ⬆️
lib 7.39% <ø> (ø)
lifecycle 18.76% <ø> (+<0.01%) ⬆️
notification 1.06% <ø> (ø)
replication 18.53% <ø> (ø)
unit 48.74% <ø> (ø)

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.

@scality scality deleted a comment from bert-e May 18, 2025
@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented May 18, 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.

Copy link
Copy Markdown

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Tests are flaky?

@francoisferrand
Copy link
Copy Markdown
Contributor Author

/approve

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented May 19, 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-687.

Goodbye francoisferrand.

The following options are set: approve

@bert-e bert-e merged commit d98bb77 into development/9.0 May 19, 2025
13 of 14 checks passed
@bert-e bert-e deleted the improvement/BB-687 branch May 19, 2025 07:49
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.

3 participants