-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
hyperkit 0.20210107 #72028
hyperkit 0.20210107 #72028
Conversation
Testing a VM inside of a VM (the CI) is probably going to be a problem here. |
Was there some progress on Big Sur that isn't yet reflected on moby/hyperkit#297 ? |
Yes, moby/hyperkit#307 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
If we can't test this in a sandbox, we may as well just get rid of the test block (or put in some trivial test that will work in a sandbox). The current bottles are failing tests anyway... |
IMO the best option would be to leave the test but skip it on CI -- that way it at least can be run manually as part of formula maintenance. However I haven't had luck in the past with getting changes like that past review: #66485 (comment) |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
There's been some changes so the VM environment so let's see if anything's changed here. |
Formula/hyperkit.rb
Outdated
system "opam", "exec", "--", | ||
"opam", "install", "uri.4.1.0", "qcow.0.11.0", "conduit.2.1.0", "lwt.5.3.0", | ||
"qcow-tool.0.11.0", "mirage-block-unix.2.12.0", "conf-libev.4-11", "logs.0.7.0", "fmt.0.8.9", | ||
"mirage-unix.4.0.0", "prometheus-app.1.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good to add a comment here about how to update these when needed.
Did we not revsion bump |
Unfortunately not: #71942 But CI didn't pick anything up with |
I suppose if it only uses the binary then there's no issues. There'll only be issues if it actually uses it as a library, and This is certainly the first formula to use the |
Oops. We should probably add |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Tried another run with updated EDIT: Haven't been able to get test to work locally, though I am trying via Rosetta layer. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingbrew install <formula>
)?