[main] Update module github.com/onsi/ginkgo/v2 to v2.33.0 (main)

[ospk8s-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/onsi/ginkgo/v2	v2.32.1 → v2.33.0

---

Release Notes

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.33.0

Compare Source

Features

• The JUnit reporter now records each spec's ReportEntrys as <properties> on its <testcase> element, with the entry's name and its JSON-encoded value. Thanks @​pohly! [23db51a]

Maintenance

• Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. See RELEASING.md. [8616ecb]

v2.32.2

Compare Source

2.32.2

Fixes

• fix bug where ginkgo -race -p was taking extra long to exit [c6792b0]

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: 210bc01f-262d-4375-a8b1-262fbc194f76

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

Hi @ospk8s-renovate[bot]. Thanks for your PR.

I'm waiting for a openstack-k8s-operators 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.

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.

[centosinfra-prod-github-app]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/c9e9f429e4514dd78aa435d8d32d81fe

✔️ openstack-meta-content-provider SUCCESS in 4h 47m 12s
✔️ nova-operator-kuttl SUCCESS in 51m 20s
✔️ nova-operator-kuttl-placement SUCCESS in 39m 22s
❌ nova-operator-tempest-multinode FAILURE in 2h 31m 33s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 2h 45m 11s
✔️ nova-operator-cyborg-tempest-multinode SUCCESS in 1h 42m 47s (non-voting)

[centosinfra-prod-github-app]

Build succeeded (check pipeline).
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/4c3f3e5b2d114e66b7fbda5e5455e270

✔️ openstack-meta-content-provider SUCCESS in 7h 48m 09s
✔️ nova-operator-kuttl SUCCESS in 52m 33s
✔️ nova-operator-kuttl-placement SUCCESS in 40m 25s
✔️ nova-operator-tempest-multinode SUCCESS in 2h 38m 39s
✔️ nova-operator-tempest-multinode-ceph SUCCESS in 3h 06m 16s
✔️ nova-operator-cyborg-tempest-multinode SUCCESS in 1h 35m 00s (non-voting)

[stuggi]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ospk8s-renovate[bot], stuggi

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 [stuggi]

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