-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Switch to lima as Vagrant replacement #1953
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f52f35e
to
83a22a3
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1953 +/- ##
=======================================
Coverage 49.25% 49.25%
=======================================
Files 72 72
Lines 7037 7037
=======================================
Hits 3466 3466
Misses 3437 3437
Partials 134 134 |
8c68b06
to
c06e474
Compare
/retest |
looks like we have e2e failed test |
Yep, working towards that. |
4bb59db
to
5543830
Compare
754f63b
to
59ab77f
Compare
Signed-off-by: Sascha Grunert <[email protected]>
There seems to be a networking issue now, locally the tests pass 🤔 |
/retest |
I'm closing this, it seems that lima is a bit slower on GitHub actions so we're facing timeout issues here. |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Giving lima a try.
Which issue(s) this PR fixes:
Refers to #1936
Does this PR have test?
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?