Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

saschagrunert
Copy link
Member

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?

None

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note-none Denotes a PR that doesn't merit a release note. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. labels Nov 1, 2023
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 1, 2023
@k8s-ci-robot k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Nov 1, 2023
@saschagrunert saschagrunert force-pushed the lima branch 3 times, most recently from f52f35e to 83a22a3 Compare November 1, 2023 12:26
@codecov-commenter
Copy link

codecov-commenter commented Nov 1, 2023

Codecov Report

Merging #1953 (d0b1d80) into main (c33f280) will not change coverage.
The diff coverage is n/a.

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           

@saschagrunert saschagrunert force-pushed the lima branch 4 times, most recently from 8c68b06 to c06e474 Compare November 1, 2023 15:06
@Vincent056
Copy link
Contributor

/retest

@Vincent056
Copy link
Contributor

=== RUN   TestSuite/TestSecurityProfilesOperator/cluster-wide:_Log_Enricher
I1101 21:04:54.515422   13626 suite_test.go:667]  "msg"="Enable log-enricher in SPOD" 
securityprofilesoperatordaemon.security-profiles-operator.x-k8s.io/spod patched
error: timed out waiting for the condition on securityprofilesoperatordaemons/spod
    suite_test.go:562: 

looks like we have e2e failed test

@saschagrunert
Copy link
Member Author

looks like we have e2e failed test

Yep, working towards that.

@saschagrunert saschagrunert force-pushed the lima branch 9 times, most recently from 4bb59db to 5543830 Compare November 2, 2023 14:14
@saschagrunert saschagrunert force-pushed the lima branch 4 times, most recently from 754f63b to 59ab77f Compare November 2, 2023 15:08
@saschagrunert
Copy link
Member Author

There seems to be a networking issue now, locally the tests pass 🤔

@Vincent056
Copy link
Contributor

/retest

@saschagrunert
Copy link
Member Author

I'm closing this, it seems that lima is a bit slower on GitHub actions so we're facing timeout issues here.

@saschagrunert saschagrunert deleted the lima branch March 28, 2024 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. release-note-none Denotes a PR that doesn't merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants