-
Notifications
You must be signed in to change notification settings - Fork 38
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
Volume Snapshot Commitment #619
Conversation
tiagolobocastro
commented
Jul 5, 2023
Make cache reload period too high so we don't try to refresh whilst testing a timeout condition. Signed-off-by: Tiago Castro <[email protected]>
bors merge |
619: Volume Snapshot Commitment r=tiagolobocastro a=tiagolobocastro feat(snapshot/commitment): use commitment when creating a snapshot The snapshot create now uses the same rules as volume/replica creation. Signed-off-by: Tiago Castro <[email protected]> --- ci: fix test race condition Make cache reload period too high so we don't try to refresh whilst testing a timeout condition. Signed-off-by: Tiago Castro <[email protected]> Co-authored-by: Tiago Castro <[email protected]>
Build failed: |
620: Cherry-pick #619 r=tiagolobocastro a=tiagolobocastro feat(snapshot/commitment): use commitment when creating a snapshot The snapshot create now uses the same rules as volume/replica creation. Signed-off-by: Tiago Castro <[email protected]> --- ci: fix test race condition Make cache reload period too high so we don't try to refresh whilst testing a timeout condition. Signed-off-by: Tiago Castro <[email protected]> Co-authored-by: Tiago Castro <[email protected]>
The snapshot create now uses the same rules as volume/replica creation. Signed-off-by: Tiago Castro <[email protected]>
4ff1569
to
c4c236f
Compare
bors merge |
619: Volume Snapshot Commitment r=tiagolobocastro a=tiagolobocastro feat(snapshot/commitment): use commitment when creating a snapshot The snapshot create now uses the same rules as volume/replica creation. Signed-off-by: Tiago Castro <[email protected]> --- ci: fix test race condition Make cache reload period too high so we don't try to refresh whilst testing a timeout condition. Signed-off-by: Tiago Castro <[email protected]> Co-authored-by: Tiago Castro <[email protected]>
This PR was included in a batch that successfully built, but then failed to merge into develop. It will not be retried. Additional information: Response status code: 422
{"message":"Required status check \"DCO\" is expected.","documentation_url":"https://docs.github.com/articles/about-protected-branches"} |
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
620: Cherry-pick #619 r=tiagolobocastro a=tiagolobocastro feat(snapshot/commitment): use commitment when creating a snapshot The snapshot create now uses the same rules as volume/replica creation. Signed-off-by: Tiago Castro <[email protected]> --- ci: fix test race condition Make cache reload period too high so we don't try to refresh whilst testing a timeout condition. Signed-off-by: Tiago Castro <[email protected]> Co-authored-by: Tiago Castro <[email protected]>
620: Cherry-pick #619 r=tiagolobocastro a=tiagolobocastro feat(snapshot/commitment): use commitment when creating a snapshot The snapshot create now uses the same rules as volume/replica creation. Signed-off-by: Tiago Castro <[email protected]> --- ci: fix test race condition Make cache reload period too high so we don't try to refresh whilst testing a timeout condition. Signed-off-by: Tiago Castro <[email protected]> Co-authored-by: Tiago Castro <[email protected]>