The detailed logs should be gathered by linuxkit-ci
and having the default output makes it easier to spot
which test failed.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
These tests should be run via rtf but currently are
run via linuxkit-ci. This is a hack and hopefully is now
marked more clearly as such.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
This was a hack in the first place and will be replaced by
another, more obvious hack in the next commit.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
This should be replaced with more comprehensive documentation in
./doc/testing.md once the CI is fixed
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
There is no need to split the build from run as we have separate build tests
Also shuffle the order around a little. Double digit numbers are for local hypervisor
tests and tripple digit tests are for cloud.
Removed GCP test as they weren't run.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
The vmlinux image is the un-stripped kernel image containing
full debug information which is useful for kernel debugging.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
For local testinf it is useful to store packages under a different
organisation on the hub (or indeed to select a different registry).
This is enabled by making the ORG configurable when calling make.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
While testing the patches on Windows we found some issues
which commit d0e6020dd2b25f8880 ("hvsock: fix a race in
hvs_stream_dequeue()") (cherry-picked as 0009) attempts to
fix.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
- Add a tests which generates all supported outputs
- move the examples build tests to the new group
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
When `-vsock-ports` is specified, the listed guest vsock
ports will be made available through unix domain sockets
in the state directory.
Signed-off-by: Magnus Skjegstad <magnus@skjegstad.com>
We were missing one repo needed for Windows; but we have also not deleted
a bunch of vendored code that we are no longer using.
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
The state directory is used to store any user data disk images
and the .vmx file. At run time, it is also used to keep
various other files, such as the nvram, log and lock files, etc.
While at it, also clean up the code a little more and fix the
handling of the "-disk-size" argument when no "-disk" argument
is specified. This brings it in line with the other runners.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
There is no need to prefix local variables and try to name
variables which refer to the same/simialr thing the same
across runners.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
The state directory is used to store:
- the disk image, if not specified via '-disk'
- the ISO for metadata, if '-data' is used
- the Unix domain socket for virtio sockets
- the PID of the hyperkit process
- a JSON file with the hyperkit configuration
This patch also enables the virtio socket device for the VM.
While at it, also fix .gitignore to ignore kernel images again.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
- What I did
Added the capability to re-use or create a disk from the linuxkit
VMware cli
- How I did it
Using the vmware-diskmanager that comes with Fusion/Workstation
- How to verify it
Run linuxkit run vmware with the -disk -disk-size arguments
- Description for the changelog
Persistent disk functionality added into the VMware backend.
- A picture of a cute animal (not mandatory but encouraged)
nope
Signed-off-by: Dan Finneran <daniel.finneran@gmail.com>
