Implementation of a function that returns the wait state of the scheduler

[gx14ac]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

I thought it would be useful to have this function when I am building my own Kubernetes scheduler, so I sent a PR.
Just as Success has an IsSuccess function, it would be nice to have an IsWait for Wait.
I am new to Kubernetes, so maybe this is a pointless change.
But I sent this PR in the hope that there is even a small chance of keeping the code clean. If it's useless, feel free to delete it!
Any reviews would be greatly appreciated!

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: shintard / name: Shinta (9480a51ee27737327e705542aefc9e76f165048f, d1255c9c50cc10a880a3925ad2d126fddd8bb0ce, 7d08a7d3b720fc9b7d9b10cac012e738e779f96d)

[k8s-ci-robot]

@shintard: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[k8s-ci-robot]

Welcome @shintard!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @shintard. Thanks for your PR.

I'm waiting for a kubernetes 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/test-infra repository.

[Huang-Wei]

/ok-to-test

[gx14ac]

/retest

[gx14ac]

The test seems to be failing, is there anything else I need to add?
For example, adding to the TestStatus and TestStatusCode test functions in pkg/scheduler/framework/interface_test.go.

[kerthcet]

/retest

[kerthcet]

The test seems to be failing, is there anything else I need to add? For example, adding to the TestStatus and TestStatusCode test functions in pkg/scheduler/framework/interface_test.go.

It's better to add tests, you can rename TestStatus to TestIsSuccessStatus in interfact_test.go and add some similar tests in TestIsWaitStatus.

[gx14ac]

It's better to add tests, you can rename TestStatus to TestIsSuccessStatus in interfact_test.go and add some similar tests in TestIsWaitStatus.

thank you.
I'll add a test!

[gx14ac]

@kerthcet I added some test code.
pls check!

[gx14ac]

thx. squashed

[denkensk]

thx. squashed

@shintard You need to squash all the commits to one.

[gx14ac]

@denkensk I misunderstood the meaning of squash.
thank you.
commit in one.

[denkensk]

/lgtm

[denkensk]

/hold cancel

[Huang-Wei]

/release-note-none

[sanposhiho]

One small nits

[sanposhiho]

(Let me remove lgtm for the above small change request.)
/remove-lgtm

[gx14ac]

@sanposhiho thx for the review.

[sanposhiho]

/retest
/lgtm

[k8s-ci-robot]

@shintard: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-integration	2298440	link	unknown	/test pull-kubernetes-integration

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[sanposhiho]

/retest

[alculquicondor]

Did you open a bug for the flaky tests?

[sanposhiho]

No.
will create an issue later.

[sanposhiho]

Created: #109785