Fix typo: succesful -> successful in prompt test description

[SAY-5]

Corrects the misspelling 'succesful' to 'successful' in a Ginkgo test description.

[k8s-ci-robot]

This issue is currently awaiting triage.

If instrumentation-tools contributors determine 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.

Details

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]

Welcome @SAY-5!

It looks like this is your first PR to kubernetes-sigs/instrumentation-tools 🎉. 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/instrumentation-tools 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. 😃

[dashpole]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dashpole, SAY-5

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dashpole]

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

[SAY-5]

Could you add ok-to-test? CI is gated on it for new contributors.

[dashpole]

I don't think thats the issue. CI seems generally broken.

Error: The actions actions/setup-go@v2.1.0 and actions/checkout@v2 are not allowed in kubernetes-sigs/instrumentation-tools because all actions must be pinned to a full-length commit SHA.

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[SAY-5]

You're right, that was the real blocker. Pushed ffa9eab pinning checkout and setup-go to full-length SHAs (v4.2.2 and v5.2.0) so they pass the org policy, and bumped go-version from 1.14 to 1.22 since the module is already on go 1.17. Dropped the stale ACTIONS_ALLOW_UNSECURE_COMMANDS env that only the old setup-go needed. go test -race ./promq/... is green locally.