Skip to content

Conversation

@sunzhaohua2
Copy link
Contributor

@sunzhaohua2 sunzhaohua2 commented Feb 2, 2026

Stacked on top of: #387

--

Try to create all resources together (parallel creation, saving time), and in each Describe block deletes its own resources immediately after testing (saving resources and costs).

ci/prow/e2e-aws-capi-techpreview e2e duration changed from ~4h10m to 3h15m.

Summary by CodeRabbit

  • Tests

    • Major e2e test refactor: shared fixtures, centralized setup/cleanup, parallel resource creation, and broader migration/status-conversion coverage.
    • Added extensive new end-to-end status-conversion and migration scenarios and more robust async waits and verifications.
  • New Features

    • Unique-name helper for parallel test resources.
    • Skip-wait variants to support faster, parallel test orchestration.
    • YAML-based provider-status verification support.
  • Chores

    • Increased e2e test timeout to accommodate longer runs.

@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 2, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 2, 2026

@sunzhaohua2: This pull request references OCPCLOUD-3354 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

@sunzhaohua2
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 2, 2026
@openshift-ci openshift-ci bot requested review from chrischdi and racheljpg February 2, 2026 08:34
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details 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

@coderabbitai
Copy link

coderabbitai bot commented Feb 2, 2026

📝 Walkthrough

Walkthrough

Centralizes e2e test fixtures with shared BeforeAll/AfterAll, adds UniqueName utility, extends helpers for YAML providerStatus and Ginkgo integration, adds skip-wait MachineSet helpers, introduces a large status-conversion e2e suite, and increases e2e timeout from 120m to 180m.

Changes

Cohort / File(s) Summary
Test Timeout Configuration
Makefile
Increased e2e timeout from 120m to 180m.
Machine Migration Tests (CAPI auth)
e2e/machine_migration_capi_authoritative_test.go
Replaced per-test locals with package-level shared fixtures; centralized BeforeAll/AfterAll setup and cleanup; tests reference shared CAPI/MAPI machines and mirrors across Create/Delete/Round‑Trip scenarios.
Machine Migration Tests (MAPI auth)
e2e/machine_migration_mapi_authoritative_test.go
Added package-level shared MAPI/CAPI fixtures, moved setup to BeforeAll and cleanup to AfterAll; refactored tests to use shared resources for Create/Delete/Round‑Trip flows.
Machine Migration Helpers
e2e/machine_migration_helpers.go
Added YAML providerStatus unmarshalling and helpers (verifyMAPIMachineProviderStatus, getAWSProviderStatusFromMachine); inserted GinkgoHelper() calls in many helper functions.
MachineSet Migration Tests (CAPI auth)
e2e/machineset_migration_capi_authoritative_test.go
Introduced top-level MachineSet/AWSMachineTemplate/Machine fixtures; parallelized creation/readiness waits; centralized cleanup; refactored Create/Scale/Delete flows to use shared mirrors and asynchronous wait/assert patterns.
MachineSet Migration Tests (MAPI auth)
e2e/machineset_migration_mapi_authoritative_test.go
Parallelized creation of multiple MAPI MachineSets and CAPI mirrors; added extensive scaffolding variables, dynamic lookups, asynchronous waits, and AfterAll cleanup across Create/Scale/Update scenarios.
MachineSet Migration Helpers
e2e/machineset_migration_helpers.go
Added skip‑wait variants (createCAPIMachineSetSkipWait, createMAPIMachineSetWithAuthoritativeAPISkipWait) and waitForMAPIMachineSetReady; existing helpers now delegate to skip-wait paths and include GinkgoHelper() calls.
Common Utilities
e2e/migration_common.go
Added public UniqueName(prefix string) string to generate nanosecond-suffixed unique names.
New Status Conversion Tests
e2e/status_conversion_test.go
Added a large e2e suite validating MAPI↔CAPI status conversions across MachineSets, Machines, and AWSMachineTemplates (authoritative and same-name scenarios, error cases, providerStatus mappings).

Estimated code review effort

🎯 5 (Critical) | ⏱️ ~120 minutes

Poem

🐰 I hopped through fixtures, one by one,
Shared seeds sown till the jobs were done.
Names stamped with nanoseconds bright,
Timeouts stretched to last the night.
Tests aligned — a migration delight! 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 77.42% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly addresses the PR's main objective: optimizing migration e2e tests to reduce running time, which is clearly supported by the substantial refactoring of test infrastructure across multiple files.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.5.0)

Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions
The command is terminated due to an error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions


Comment @coderabbitai help to get the list of available commands and usage tips.

@sunzhaohua2
Copy link
Contributor Author

/test e2e-aws-capi-techpreview

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 2, 2026

@sunzhaohua2: This pull request references OCPCLOUD-3354 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

Release Notes

  • Tests

  • Enhanced end-to-end test coverage for machine migration scenarios with improved resource management and parallel test execution

  • Added comprehensive status conversion testing across resource types

  • Chores

  • Increased end-to-end test timeout to support longer-running test scenarios

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
e2e/migration_common.go (1)

3-24: ⚠️ Potential issue | 🟡 Minor

UniqueName isn’t guaranteed unique under heavy parallelism.
UnixNano can collide when multiple goroutines call within the same nanosecond, which can create occasional “AlreadyExists” flakes. Consider adding a per-process counter (or random suffix) to make collisions practically impossible.

💡 Suggested fix (monotonic counter suffix)
 import (
 	"fmt"
+	"sync/atomic"
 	"time"
 )
 
+var uniqueCounter atomic.Uint64
+
 // UniqueName generates a unique name with the given prefix using nanosecond timestamp.
 // This is useful for creating resources in parallel tests without naming conflicts.
 func UniqueName(prefix string) string {
-	return fmt.Sprintf("%s-%d", prefix, time.Now().UnixNano())
+	return fmt.Sprintf("%s-%d-%d", prefix, time.Now().UnixNano(), uniqueCounter.Add(1))
 }
🤖 Fix all issues with AI agents
In `@e2e/machine_migration_helpers.go`:
- Around line 356-363: The function getAWSProviderStatusFromMachine dereferences
mapiMachine.Status.ProviderStatus.Raw without checking for nil, causing a panic
when ProviderStatus is not yet populated; modify getAWSProviderStatusFromMachine
to first check if mapiMachine.Status.ProviderStatus is nil (and/or if .Raw is
nil/empty) and handle that case by returning nil or a clear test failure using
Expect with a helpful message, before attempting yaml.Unmarshal into
mapiv1beta1.AWSMachineProviderStatus.

In `@e2e/machineset_migration_capi_authoritative_test.go`:
- Around line 100-117: The test is fragile because it compares slices by fixed
index; replace index-based equality checks between mapiMachines and capiMachines
(variables mapiMachines, capiMachines, mapiMachinesDelete, capiMachinesDelete)
with membership/set-based assertions: extract names from the CAPI slices and
assert each MAPI machine's name is present using
Expect(...).To(ContainElement(...)) or compare as sets/maps, and for
firstMAPIMachine assign the MAPI machine found by matching a name from
capiMachines (not mapiMachines[0]) so the selected machine is stable
irrespective of slice ordering.

In `@e2e/machineset_migration_mapi_authoritative_test.go`:
- Around line 106-114: The test currently assumes ordering by comparing
capiMachines[0].Name to mapiMachines[0].Name (using
mapiframework.GetMachinesFromMachineSet and
capiframework.GetMachinesFromMachineSet), which can flake; instead, assert
membership by checking that every MAPI machine name appears in the CAPI machines
(or vice‑versa) using a set/contains check on names, and then pick a matching
MAPI machine (e.g., the one whose name exists in the CAPI name set) to assign to
firstMAPIMachine; update the Expect assertions to use membership-based checks
rather than index-based equality.

In `@e2e/status_conversion_test.go`:
- Around line 629-648: The test reads
mapiMachineAuthMAPI.Status.ProviderStatus.Raw without guarding for nil which can
panic; before calling yaml.Unmarshal into mapiProviderStatus, add a nil/empty
check or an Eventually/Expect that waits for
mapiMachineAuthMAPI.Status.ProviderStatus (and/or ProviderStatus.Raw) to be
non-nil/non-empty (referencing mapiMachineAuthMAPI.Status.ProviderStatus.Raw and
the yaml.Unmarshal call into mapiProviderStatus) and only then perform the
Unmarshal and subsequent assertions.

Comment on lines +629 to +648
It("should convert MAPI Machine providerStatus to CAPI AWSMachine status", func() {
By("Getting AWSMachine for the CAPI Machine")
awsMachine := capiframework.GetAWSMachine(cl, capiMachineMirrorMAPI.Name, capiframework.CAPINamespace)
Expect(awsMachine).NotTo(BeNil(), "AWSMachine should exist")

By("Verifying AWSMachine status.ready is set based on MAPI Machine providerStatus.instanceState")
Eventually(komega.Object(awsMachine), capiframework.WaitMedium, capiframework.RetryMedium).Should(
HaveField("Status.Ready", BeTrue()),
"Should have AWSMachine status.ready be true when instance is running",
)

By("Verifying AWSMachine status.instanceState matches MAPI Machine providerStatus.instanceState")
var mapiProviderStatus mapiv1beta1.AWSMachineProviderStatus
err := yaml.Unmarshal(mapiMachineAuthMAPI.Status.ProviderStatus.Raw, &mapiProviderStatus)
Expect(err).ToNot(HaveOccurred())

Eventually(komega.Object(awsMachine), capiframework.WaitMedium, capiframework.RetryMedium).Should(
HaveField("Status.InstanceState", HaveValue(Equal(awsv1.InstanceState(ptr.Deref(mapiProviderStatus.InstanceState, ""))))),
"Should have AWSMachine status.instanceState match MAPI providerStatus.instanceState",
)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add a nil guard before reading ProviderStatus.Raw.
If ProviderStatus hasn’t been populated yet, dereferencing .Raw will panic and hard-fail the test.

🛡️ Suggested fix
-				var mapiProviderStatus mapiv1beta1.AWSMachineProviderStatus
-				err := yaml.Unmarshal(mapiMachineAuthMAPI.Status.ProviderStatus.Raw, &mapiProviderStatus)
+				Expect(mapiMachineAuthMAPI.Status.ProviderStatus).NotTo(BeNil())
+				var mapiProviderStatus mapiv1beta1.AWSMachineProviderStatus
+				err := yaml.Unmarshal(mapiMachineAuthMAPI.Status.ProviderStatus.Raw, &mapiProviderStatus)
 				Expect(err).ToNot(HaveOccurred())
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
It("should convert MAPI Machine providerStatus to CAPI AWSMachine status", func() {
By("Getting AWSMachine for the CAPI Machine")
awsMachine := capiframework.GetAWSMachine(cl, capiMachineMirrorMAPI.Name, capiframework.CAPINamespace)
Expect(awsMachine).NotTo(BeNil(), "AWSMachine should exist")
By("Verifying AWSMachine status.ready is set based on MAPI Machine providerStatus.instanceState")
Eventually(komega.Object(awsMachine), capiframework.WaitMedium, capiframework.RetryMedium).Should(
HaveField("Status.Ready", BeTrue()),
"Should have AWSMachine status.ready be true when instance is running",
)
By("Verifying AWSMachine status.instanceState matches MAPI Machine providerStatus.instanceState")
var mapiProviderStatus mapiv1beta1.AWSMachineProviderStatus
err := yaml.Unmarshal(mapiMachineAuthMAPI.Status.ProviderStatus.Raw, &mapiProviderStatus)
Expect(err).ToNot(HaveOccurred())
Eventually(komega.Object(awsMachine), capiframework.WaitMedium, capiframework.RetryMedium).Should(
HaveField("Status.InstanceState", HaveValue(Equal(awsv1.InstanceState(ptr.Deref(mapiProviderStatus.InstanceState, ""))))),
"Should have AWSMachine status.instanceState match MAPI providerStatus.instanceState",
)
It("should convert MAPI Machine providerStatus to CAPI AWSMachine status", func() {
By("Getting AWSMachine for the CAPI Machine")
awsMachine := capiframework.GetAWSMachine(cl, capiMachineMirrorMAPI.Name, capiframework.CAPINamespace)
Expect(awsMachine).NotTo(BeNil(), "AWSMachine should exist")
By("Verifying AWSMachine status.ready is set based on MAPI Machine providerStatus.instanceState")
Eventually(komega.Object(awsMachine), capiframework.WaitMedium, capiframework.RetryMedium).Should(
HaveField("Status.Ready", BeTrue()),
"Should have AWSMachine status.ready be true when instance is running",
)
By("Verifying AWSMachine status.instanceState matches MAPI Machine providerStatus.instanceState")
Expect(mapiMachineAuthMAPI.Status.ProviderStatus).NotTo(BeNil())
var mapiProviderStatus mapiv1beta1.AWSMachineProviderStatus
err := yaml.Unmarshal(mapiMachineAuthMAPI.Status.ProviderStatus.Raw, &mapiProviderStatus)
Expect(err).ToNot(HaveOccurred())
Eventually(komega.Object(awsMachine), capiframework.WaitMedium, capiframework.RetryMedium).Should(
HaveField("Status.InstanceState", HaveValue(Equal(awsv1.InstanceState(ptr.Deref(mapiProviderStatus.InstanceState, ""))))),
"Should have AWSMachine status.instanceState match MAPI providerStatus.instanceState",
)
🤖 Prompt for AI Agents
In `@e2e/status_conversion_test.go` around lines 629 - 648, The test reads
mapiMachineAuthMAPI.Status.ProviderStatus.Raw without guarding for nil which can
panic; before calling yaml.Unmarshal into mapiProviderStatus, add a nil/empty
check or an Eventually/Expect that waits for
mapiMachineAuthMAPI.Status.ProviderStatus (and/or ProviderStatus.Raw) to be
non-nil/non-empty (referencing mapiMachineAuthMAPI.Status.ProviderStatus.Raw and
the yaml.Unmarshal call into mapiProviderStatus) and only then perform the
Unmarshal and subsequent assertions.

@sunzhaohua2 sunzhaohua2 force-pushed the refactor-migration-tests branch from 4d785aa to 20ae306 Compare February 2, 2026 10:43
@sunzhaohua2
Copy link
Contributor Author

/test e2e-aws-capi-techpreview

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 2, 2026

@sunzhaohua2: This pull request references OCPCLOUD-3354 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

  • Tests

  • Major e2e test refactor: shared test scaffolding, parallel resource creation, centralized setup/cleanup, and expanded status-conversion and migration scenarios.

  • Added YAML-based provider-status checks and more robust asynchronous waits/verifications.

  • New Features

  • Added a helper to generate unique resource names for parallel tests.

  • Added skip-wait variants to enable faster parallel test orchestration.

  • Chores

  • Increased e2e test timeout to accommodate longer runs.

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 openshift-eng/jira-lifecycle-plugin repository.

@sunzhaohua2 sunzhaohua2 force-pushed the refactor-migration-tests branch from 20ae306 to bfdcece Compare February 2, 2026 12:45
@sunzhaohua2
Copy link
Contributor Author

/test e2e-aws-capi-techpreview

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 2, 2026

@sunzhaohua2: This pull request references OCPCLOUD-3354 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

  • Tests

  • Major e2e test refactor: shared test scaffolding, centralized setup/cleanup, parallel resource creation, and expanded status-conversion and migration scenarios.

  • Added YAML-based provider-status verification and more robust asynchronous waits/verifications.

  • New Features

  • Helper to generate unique resource names for parallel tests.

  • Skip-wait variants to enable faster, parallel test orchestration.

  • Chores

  • Increased e2e test timeout to accommodate longer runs.

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 openshift-eng/jira-lifecycle-plugin repository.

@sunzhaohua2 sunzhaohua2 force-pushed the refactor-migration-tests branch from bfdcece to 58501da Compare February 2, 2026 15:01
@sunzhaohua2
Copy link
Contributor Author

/test e2e-aws-capi-techpreview

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 2, 2026

@sunzhaohua2: This pull request references OCPCLOUD-3354 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

  • Tests

  • Major e2e test refactor: shared fixtures, centralized setup/cleanup, parallel resource creation, and broader migration/status-conversion coverage.

  • Added extensive new end-to-end status-conversion and migration scenarios and more robust async waits and verifications.

  • New Features

  • Unique-name helper for parallel test resources.

  • Skip-wait variants to support faster, parallel test orchestration.

  • YAML-based provider-status verification support.

  • Chores

  • Increased e2e test timeout to accommodate longer runs.

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 openshift-eng/jira-lifecycle-plugin repository.

@sunzhaohua2
Copy link
Contributor Author

ci/prow/e2e-aws-capi-techpreview e2e duration changed from ~4h10m to 3h15m.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 3, 2026

@sunzhaohua2: This pull request references OCPCLOUD-3354 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Try to create all resources together (parallel creation, saving time), and in each Describe block deletes its own resources immediately after testing (saving resources and costs).

ci/prow/e2e-aws-capi-techpreview e2e duration changed from ~4h10m to 3h15m.

Summary by CodeRabbit

  • Tests

  • Major e2e test refactor: shared fixtures, centralized setup/cleanup, parallel resource creation, and broader migration/status-conversion coverage.

  • Added extensive new end-to-end status-conversion and migration scenarios and more robust async waits and verifications.

  • New Features

  • Unique-name helper for parallel test resources.

  • Skip-wait variants to support faster, parallel test orchestration.

  • YAML-based provider-status verification support.

  • Chores

  • Increased e2e test timeout to accommodate longer runs.

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/assign @RadekManak @nrb

@damdo
Copy link
Member

damdo commented Feb 4, 2026

Depends on #387

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 4, 2026

@sunzhaohua2: This pull request references OCPCLOUD-3354 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Stacked on top of: #387

--

Try to create all resources together (parallel creation, saving time), and in each Describe block deletes its own resources immediately after testing (saving resources and costs).

ci/prow/e2e-aws-capi-techpreview e2e duration changed from ~4h10m to 3h15m.

Summary by CodeRabbit

  • Tests

  • Major e2e test refactor: shared fixtures, centralized setup/cleanup, parallel resource creation, and broader migration/status-conversion coverage.

  • Added extensive new end-to-end status-conversion and migration scenarios and more robust async waits and verifications.

  • New Features

  • Unique-name helper for parallel test resources.

  • Skip-wait variants to support faster, parallel test orchestration.

  • YAML-based provider-status verification support.

  • Chores

  • Increased e2e test timeout to accommodate longer runs.

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 openshift-eng/jira-lifecycle-plugin repository.


// getAWSProviderStatusFromMachine extracts and unmarshals the AWSMachineProviderStatus from a MAPI Machine.
func getAWSProviderStatusFromMachine(mapiMachine *mapiv1beta1.Machine) *mapiv1beta1.AWSMachineProviderStatus {
Expect(mapiMachine.Status.ProviderStatus.Raw).ToNot(BeNil())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could call GinkgoHelper() here as well or any specific reason not using it here ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@miyadav this is a stack PR on top of #387
Which originally introduces the Ginkgo helper part, probably worth commenting there

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah got it , Nolan already did , thanks Dam

.PHONY: e2e
e2e: ## Run e2e tests against active kubeconfig
./hack/test.sh "./e2e/..." 120m
./hack/test.sh "./e2e/..." 180m
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for CI we may want to increase this bit more ? May be we can conclude after all pre-submits are passed like 20% more time than they took ?

@RadekManak
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2026
@openshift-ci-robot
Copy link

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-capi-techpreview
/test e2e-aws-ovn
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-techpreview
/test e2e-aws-ovn-techpreview-upgrade
/test e2e-azure-capi-techpreview
/test e2e-azure-ovn-techpreview
/test e2e-azure-ovn-techpreview-upgrade
/test e2e-gcp-capi-techpreview
/test e2e-gcp-ovn-techpreview
/test e2e-metal3-capi-techpreview
/test e2e-openstack-capi-techpreview
/test e2e-openstack-ovn-techpreview
/test e2e-vsphere-capi-techpreview
/test regression-clusterinfra-aws-ipi-techpreview-capi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 4, 2026

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

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-techpreview 58501da link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-vsphere-capi-techpreview 58501da link true /test e2e-vsphere-capi-techpreview
ci/prow/e2e-aws-capi-techpreview 58501da link true /test e2e-aws-capi-techpreview
ci/prow/e2e-openstack-ovn-techpreview 58501da link true /test e2e-openstack-ovn-techpreview
ci/prow/e2e-azure-ovn-techpreview 58501da link false /test e2e-azure-ovn-techpreview

Full PR test history. Your PR dashboard.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants