Skip to content

Conversation

@mkroening
Copy link
Member

Since Uhyve is flaky on GitHub runners (hermit-os/uhyve#1150), we should either run it early to fail early (hermit-os/kernel#2003) or not run it at all.

This PR makes us not test on Uhyve at all. Since this is only the collection of example applications with no Uhyve-specific code, this might be the easiest. They will, of course, still be run comprehensively in the kernel CI.

I don't feel strongly about this, though. If you disagree, I'll just move the Uhyve run to the start.

@mkroening mkroening self-assigned this Nov 17, 2025
@jounathaen
Copy link
Member

We can also (temporarily) run the uhyve tests on our custom runners. They seem to be stable there, right?

@mkroening
Copy link
Member Author

Yes, but I would not like to use self-hosted runners here.

If you are opposed to dropping Uhyve CI from this repo, I'd rather just move them to the start. :)

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.

3 participants