Skip to content

Conversation

Zerpet
Copy link
Member

@Zerpet Zerpet commented Aug 28, 2025

Summary Of Changes

  • Make integration tests parallel
  • Make unit tests parallel
  • go mod tidy

Additional Context

The execution time of integration tests goes down from 10 minutes to 1m30s on average.

Local Testing

Please ensure you run the unit, integration and system tests before approving the PR.

To run the unit and integration tests:

make unit-tests integration-tests

@Zerpet Zerpet added this to the 2.17.0 milestone Aug 28, 2025
@Zerpet Zerpet marked this pull request as draft August 29, 2025 12:48
@Zerpet
Copy link
Member Author

Zerpet commented Aug 29, 2025

Converting to a draft because the integration suite in parallel has become very flaky

Used ginkgolinter.
The main problem were flakes were testenv did not delete rabbitmqcluster
objects, even after issuing a delete command and waiting for 5 seconds.
The "solution" is to not delete the rabbitmqcluster objects. Instead,
create objects with unique names.

I also updated the default k8s version for testenv from 1.26 to 1.29.
Current stable version of upstream Kubernetes in 1.34. Testing on N-5 is
very decent to maintain the backwards compatibility promise. Earlier
Kubernetes versions are EOL'ed.
@Zerpet Zerpet force-pushed the parallel-integration-suite branch from 5e1cf49 to ec27bfa Compare September 10, 2025 15:24
@Zerpet Zerpet marked this pull request as ready for review September 10, 2025 15:33
@Zerpet
Copy link
Member Author

Zerpet commented Sep 10, 2025

After ec27bfa, integration tests passed locally 10 times in a row in my machine. This PR is ready now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants