Skip to content

Conversation

@AkihiroSuda
Copy link
Member

Also updated to:

  • use the latest Colima
  • test port forwarding

@AkihiroSuda AkihiroSuda added this to the v2.0.2 milestone Nov 21, 2025
@AkihiroSuda AkihiroSuda added the area/test Tests and CI label Nov 21, 2025
@AkihiroSuda AkihiroSuda modified the milestones: v2.0.2, v2.1.0 (?) Nov 24, 2025
@AkihiroSuda AkihiroSuda requested a review from a team December 1, 2025 07:13
Also updated to:
- use the latest Colima
- test port forwarding

Signed-off-by: Akihiro Suda <[email protected]>
@AkihiroSuda
Copy link
Member Author

ping @lima-vm/reviewers This has been open for a month

@norio-nomura
Copy link
Contributor

I don't understand the meaning of including colima's test in the PR merge conditions.

Previously, when my PR stopped passing only the colima test, I didn't know why the test failed from the log, and I didn't know why it healed on its own.

If some tests including colima do not pass in PR, the colima test will usually be fixed if other tests are fixed.
The problem is if only the colima test does not pass, and the current colima test does not provide enough information to find out the cause, and I think the investigation should be done by the colima project.

If the colima test is scheduled to run once a day in the master branch, we will notice that it is broken.
I think the colima test should be removed from the PR merge conditions.

@AkihiroSuda AkihiroSuda modified the milestones: v2.0.3, v2.1.0 Dec 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/test Tests and CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants