test: Including test options into the scheduling benchmark context

[DerekFrank]

Fixes #N/A

Description

The recent ODCR PR #1911 broke the scheduling benchmarking test by adding a requirement for scheduling to have options in its context.

This change introduces the standard test.Options() into the context prior to the benchmarking test,

How was this change tested?

I ran both make test and the actual scheduling test and both passed:

go test -tags=test_performance -run=SchedulingProfile
scheduled 40151 against 8031 nodes in total in 40.306934825s 996.1313152270939 pods/sec
400 instances 1 pods      1 nodes     96.906µs per scheduling      96.906µs per pod
400 instances 50 pods     10 nodes    27.13001ms per scheduling    542.6µs per pod
400 instances 100 pods    20 nodes    60.294949ms per scheduling   602.949µs per pod
400 instances 500 pods    100 nodes   257.862183ms per scheduling  515.724µs per pod
400 instances 1000 pods   200 nodes   621.7505ms per scheduling    621.75µs per pod
400 instances 1500 pods   300 nodes   784.344291ms per scheduling  522.896µs per pod
400 instances 2000 pods   400 nodes   1.013751666s per scheduling  506.875µs per pod
400 instances 5000 pods   1000 nodes  3.449692875s per scheduling  689.938µs per pod
400 instances 10000 pods  2000 nodes  8.076069042s per scheduling  807.606µs per pod
400 instances 20000 pods  4000 nodes  24.2633625s per scheduling   1.213168ms per pod
PASS
ok  	sigs.k8s.io/karpenter/pkg/controllers/provisioning/scheduling	50.701s

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: DerekFrank (a65b852)

[k8s-ci-robot]

Welcome @DerekFrank!

It looks like this is your first PR to kubernetes-sigs/karpenter 🎉. 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-sigs/karpenter 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 @DerekFrank. 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.

[dims]

/ok-to-test

[engedaam]

/lgtm

[DerekFrank]

/assign @ellistarn

[tzneal]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DerekFrank, engedaam, tzneal

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tzneal]

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