Skip to content

Conversation

@BourgoisMickael
Copy link
Contributor

@BourgoisMickael BourgoisMickael commented Sep 25, 2025

To replace condition on S3_END_TO_END with by cold storage feature presence

To run header validation tests even in S3C

No new tests, just reorganization

Test should fail if version id is invalid doesn't need to fakeMetadataArchive, it's been simplified.

The big diff is indentation

@codecov
Copy link

codecov bot commented Sep 25, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.31%. Comparing base (23fc025) to head (a817615).
⚠️ Report is 6 commits behind head on development/9.0.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph

@@               Coverage Diff                @@
##           development/9.0    #5953   +/-   ##
================================================
  Coverage            83.31%   83.31%           
================================================
  Files                  189      189           
  Lines                12147    12147           
================================================
  Hits                 10120    10120           
  Misses                2027     2027           
Flag Coverage Δ
ceph-backend-test 65.78% <ø> (ø)
file-ft-tests 66.69% <ø> (+0.25%) ⬆️
kmip-ft-tests 27.02% <ø> (ø)
mongo-v0-ft-tests 68.00% <ø> (-0.03%) ⬇️
mongo-v1-ft-tests 68.00% <ø> (ø)
multiple-backend 35.53% <ø> (ø)
quota-tests 32.28% <ø> (-0.89%) ⬇️
quota-tests-inflights 34.25% <ø> (ø)
unit 67.42% <ø> (ø)
utapi-v2-tests 33.42% <ø> (ø)

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.

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 reorganizes cold storage tests by replacing the condition based on S3_END_TO_END environment variable with checking for cold storage feature presence using config.hasColdStorage. The changes enable header validation tests to run even in S3C environments while properly separating cold storage-specific functionality.

  • Replaced process.env.S3_END_TO_END conditions with config.hasColdStorage checks
  • Moved header validation tests outside of cold storage conditional blocks
  • Reorganized test structure to separate general validation from cold storage-specific tests

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
putVersion.js Reorganized PUT object version tests to separate header validation from cold storage functionality
mpuVersion.js Reorganized multipart upload version tests with same pattern as putVersion.js
copyPart.js Updated cold storage test conditions to use config-based feature detection

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

@BourgoisMickael BourgoisMickael force-pushed the improvement/CLDSRV-741-tests-restore branch from dcd6575 to f1df2a9 Compare September 25, 2025 22:08
@BourgoisMickael BourgoisMickael requested review from a team, DarkIsDude, Kerkesni, dvasilas, fredmnl and williamlardier and removed request for a team September 26, 2025 16:16
@BourgoisMickael BourgoisMickael force-pushed the improvement/CLDSRV-741-notification-block-events branch from de2bbb1 to 8d966fb Compare September 26, 2025 18:36
To replace condition on S3_END_TO_END with by cold storage condition

To run header validation tests even in S3C

No new tests, just reorganization
@BourgoisMickael BourgoisMickael force-pushed the improvement/CLDSRV-741-tests-restore branch from f1df2a9 to a817615 Compare September 27, 2025 01:46
@BourgoisMickael BourgoisMickael changed the base branch from improvement/CLDSRV-741-notification-block-events to development/9.0 September 27, 2025 01:46
@bert-e
Copy link
Contributor

bert-e commented Sep 27, 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 27, 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.

@BourgoisMickael
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

Conflict

A conflict has been raised during the creation of
integration branch w/9.1/improvement/CLDSRV-741-tests-restore with contents from improvement/CLDSRV-741-tests-restore
and development/9.1.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.1/improvement/CLDSRV-741-tests-restore origin/development/9.1
 git merge origin/improvement/CLDSRV-741-tests-restore
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.1/improvement/CLDSRV-741-tests-restore

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

Build failed

The build for commit did not succeed in branch w/9.1/improvement/CLDSRV-741-tests-restore

The following options are set: approve

@BourgoisMickael
Copy link
Contributor Author

/create_pull_requests

@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

Follow integration pull requests if you would like to be notified of
build statuses by email.

The following options are set: approve, create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Sep 29, 2025

Build failed

The build for commit did not succeed in branch w/9.1/improvement/CLDSRV-741-tests-restore

The following options are set: approve, create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Sep 30, 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, create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Sep 30, 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 30, 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 db120d3 into development/9.0 Sep 30, 2025
27 checks passed
@bert-e bert-e deleted the improvement/CLDSRV-741-tests-restore branch September 30, 2025 03:14
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.

5 participants