Add CI tests for rusty-hermit running on uhyve.

[hermit-os]

Add CI tests for rusty-hermit running on uhyve.

[jschwe]

I'm currently working on two Travis CI pipelines.
The first one builds everything as described in the Readme, i.e.

• Build rusty-hermit demo with rust nightly from rustup and run with uhyve from cargo

The second pipeline compiles everything from source so that regressions due to changes in uhyve or in the rust repo can be quickly identified.

• The rust compiler fork from hermitcore is used
• uhyve and rusty-hermit are built from source with the the newly built compiler
• run rusty-hermit demo on uhyve

@stlankes What do you think about this? And which method of pinning the dependencies (rust and uhyve) do you prefer? I've thought of the following options:

• Add another repo that includes rusty-hermit, hermitcore/rust and uhyve as submodules. (This is the solution that I'm currently working with)
• Add rust and uhyve as submodules to this repo
• Make a config file in this repo
• Hardcode the branches that should be checked out for rust and uhyve in the travis pipeline ( This is a bit too unflexible in my opinion)

[stlankes]

@jschwe I removed Travis CI support because we have our own pipeline. Using uhyve is not so easy in CI environment. As fas as I know, Travis CI doesn't support nested virtualization. In our environment, we are able to support nested virtualization. It is currently deactivated because we are reconfiguring our setup. @stv0g is our CI expert.

We provide also the compiler as docker image. But this image based on the original nightly compiler and doesn't run any tests.

[jschwe]

Of the major CI providers to my knowledge only Travis CI provides nested virtualization by default. This seems to be somewhat recent too (late 2019 or early 2020 from what I can tell).
Based on your comment I'm assuming you are working on configuring your self hosted gitlab runner to provide nested virtualization, is this correct? Using that would of course be preferred, I just chose Travis because it works by default.

Basically this issue also isn't about which CI provider should be used, but I think it would be good if there where a CI test that tests rusty-hermit running on uhyve, both on current nightly rust builds as well as the current compiler and uhyve version in the repository. This requires specifying the dependency in some form, e.g. via submodules or a config file.

[stlankes]

I agree. I will talk @stv0g if we are enable tests with uhyve on our CI.

[stlankes]

@jschwe Do we solve this issue?

[jschwe]

Ah yes, thanks for reminding me. CI tests with uhyve were added so I'm closing the issue.