Skip to content
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

Use scaledMsPerDay when restore-adjust #5543

Conversation

KillianG
Copy link
Contributor

Use scaledMsPerday when restoring an object that has already been restored to be able to make the time go faster for testing purpose

Issue: CLDSRV-512

@bert-e
Copy link
Contributor

bert-e commented Feb 26, 2024

Hello killiang,

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.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Feb 26, 2024

Waiting for approval

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

  • the author

  • 2 peers

@KillianG KillianG force-pushed the improvement/CLDSRV-512-use-TPF-variable-when-restore-adjust branch 4 times, most recently from a544aa9 to 5122738 Compare February 26, 2024 15:50
@KillianG KillianG changed the base branch from development/8.8 to development/8.7 February 27, 2024 09:21
@KillianG KillianG force-pushed the improvement/CLDSRV-512-use-TPF-variable-when-restore-adjust branch from 5122738 to ad7c6f4 Compare February 27, 2024 09:24
@KillianG KillianG changed the base branch from development/8.7 to development/8.8 February 27, 2024 09:24
@KillianG KillianG changed the base branch from development/8.8 to development/8.7 February 27, 2024 09:25
KillianG added 2 commits February 27, 2024 10:26
Use scaledMsPerday when restoring an object that has already been restored to be able to make the time go faster for testing purpose

Issue: CLDSRV-512
@KillianG KillianG force-pushed the improvement/CLDSRV-512-use-TPF-variable-when-restore-adjust branch from ad7c6f4 to a246e18 Compare February 27, 2024 09:27
@scality scality deleted a comment from bert-e Feb 27, 2024
@bert-e
Copy link
Contributor

bert-e commented Feb 27, 2024

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.

@scality scality deleted a comment from bert-e Feb 27, 2024
@scality scality deleted a comment from bert-e Feb 27, 2024
Copy link
Contributor

@williamlardier williamlardier left a comment

Choose a reason for hiding this comment

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

As per our discussion, maybe you also want to bump the project version before merging if we need that to test at the Zenko level?

@KillianG
Copy link
Contributor Author

/create_integration_branches

@scality scality deleted a comment from bert-e Feb 27, 2024
@bert-e
Copy link
Contributor

bert-e commented Feb 27, 2024

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

@KillianG
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Feb 27, 2024

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/8.7

  • ✔️ development/8.8

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.6

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 Feb 27, 2024

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

  • ✔️ development/8.7

  • ✔️ development/8.8

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 CLDSRV-512.

Goodbye killiang.

@bert-e bert-e merged commit a009527 into development/8.7 Feb 27, 2024
19 checks passed
@bert-e bert-e deleted the improvement/CLDSRV-512-use-TPF-variable-when-restore-adjust branch February 27, 2024 10:50
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