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

[WIP] [CNS-UnRegisterVolume-API]: Automation tests for CNS-UnRegisterVolume API Feature #3029

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rpanduranga
Copy link
Contributor

[WIP] [CNS-UnRegisterVolume-API]: Automation tests for CNS-UnRegisterVolume API Feature

What this PR does / why we need it:
New automation tests

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done:
[WIP]

Special notes for your reviewer:
NA

Release note:
NA

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Sep 5, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rpanduranga
Once this PR has been reviewed and has the lgtm label, please assign sipriyaa for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link
Contributor

Hi @rpanduranga. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 5, 2024
@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch 9 times, most recently from 1c13c2b to 63e5194 Compare September 6, 2024 04:03
@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 6, 2024
@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch 3 times, most recently from 1ea2231 to ed1dfe0 Compare September 9, 2024 08:11
@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Sep 9, 2024
@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch 6 times, most recently from d3ed0cd to 5485d1d Compare September 10, 2024 11:02
@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch 3 times, most recently from faa9e16 to 2d46e6a Compare September 19, 2024 11:06
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch 2 times, most recently from d79dbc6 to 70344c2 Compare September 25, 2024 07:45
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

3 similar comments
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch from 70344c2 to e6d066f Compare September 25, 2024 09:01
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

2 similar comments
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch from e6d066f to 508ca06 Compare September 25, 2024 10:40
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch from 508ca06 to a8f1f53 Compare September 25, 2024 11:03
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch from a8f1f53 to f116c0a Compare September 25, 2024 11:30
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@rpanduranga rpanduranga force-pushed the cns_unregister_api_tests branch from f116c0a to f6da879 Compare September 25, 2024 11:51
@svcbot-qecnsdp
Copy link

Started GC block pipeline...

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 24, 2024
@k8s-ci-robot
Copy link
Contributor

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 22, 2025
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants