Back to build
Raw log | Switch to full mode | Login

Running main() from gtest_main.cc [==========] Running 21 tests from 1 test case. [----------] Global test environment set-up. [----------] 21 tests from GuestConfigParserTest [ RUN ] GuestConfigParserTest.DefaultValues [ OK ] GuestConfigParserTest.DefaultValues (0 ms) [ RUN ] GuestConfigParserTest.ParseConfig [ OK ] GuestConfigParserTest.ParseConfig (1 ms) [ RUN ] GuestConfigParserTest.ParseArgs [ OK ] GuestConfigParserTest.ParseArgs (0 ms) [ RUN ] GuestConfigParserTest.UnknownArgument [ERROR:garnet/bin/guest/vmm/guest_config.cc(341)] Unknown option --invalid-arg usage: exe_name [OPTIONS] OPTIONS: --block=[spec] Adds a block device with the given parameters --cmdline-add=[string] Adds 'string' to the existing kernel command line. This will overwrite any existing command line created using --cmdline or --cmdline-add --cmdline=[string] Use 'string' as the kernel command line --cpus=[number] Number of virtual CPUs available to the guest --dtb-overlay=[path] Load a DTB overlay for a Linux kernel --host-memory Directly map host memory into the guest --linux=[path] Load a Linux kernel from 'path' --legacy-net Enable legacy virtio-net (uses host interface) --memory=[bytes] Allocate 'bytes' of memory for the guest. The suffixes 'k', 'M', and 'G' are accepted --interrupt=[spec] Adds a hardware interrupt mapping to the guest --ramdisk=[path] Load 'path' as an initial RAM disk --virtio-balloon Enable virtio-balloon (default) --virtio-console Enable virtio-console (default) --virtio-gpu Enable virtio-gpu and virtio-input (default) --virtio-net Enable virtio-net (default) --virtio-rng Enable virtio-rng (default) --virtio-vsock Enable virtio-vsock (default) --zircon=[path] Load a Zircon kernel from 'path' BLOCK SPEC Block devices can be specified by path: /pkg/data/disk.img Additional Options: rw/ro: Create a read/write or read-only device. fdio: Use the FDIO back-end for the block device. Ex: To open a filesystem resource packaged with the guest application (read-only is important here as the /pkg/data namespace provides read-only view into the package resources): /pkg/data/system.img,fdio,ro To specify a block device with a given path and read-write permissions /dev/class/block/000,fdio,rw [ OK ] GuestConfigParserTest.UnknownArgument (0 ms) [ RUN ] GuestConfigParserTest.BooleanFlag [ OK ] GuestConfigParserTest.BooleanFlag (0 ms) [ RUN ] GuestConfigParserTest.CommandLineAppend [ OK ] GuestConfigParserTest.CommandLineAppend (0 ms) [ RUN ] GuestConfigParserTest.BlockSpecArg [ OK ] GuestConfigParserTest.BlockSpecArg (0 ms) [ RUN ] GuestConfigParserTest.BlockSpecJson [ OK ] GuestConfigParserTest.BlockSpecJson (0 ms) [ RUN ] GuestConfigParserTest.InterruptSpecArg [ OK ] GuestConfigParserTest.InterruptSpecArg (0 ms) [ RUN ] GuestConfigParserTest.InterruptSpecJson [ OK ] GuestConfigParserTest.InterruptSpecJson (0 ms) [ RUN ] GuestConfigParserTest.Memory_1024k [ OK ] GuestConfigParserTest.Memory_1024k (0 ms) [ RUN ] GuestConfigParserTest.Memory_2M [ OK ] GuestConfigParserTest.Memory_2M (0 ms) [ RUN ] GuestConfigParserTest.Memory_4G [ OK ] GuestConfigParserTest.Memory_4G (0 ms) [ RUN ] GuestConfigParserTest.Memory_AddressAndSize [ OK ] GuestConfigParserTest.Memory_AddressAndSize (0 ms) [ RUN ] GuestConfigParserTest.Memory_HostCached [ OK ] GuestConfigParserTest.Memory_HostCached (0 ms) [ RUN ] GuestConfigParserTest.Memory_HostDevice [ OK ] GuestConfigParserTest.Memory_HostDevice (1 ms) [ RUN ] GuestConfigParserTest.Memory_MultipleEntries [ OK ] GuestConfigParserTest.Memory_MultipleEntries (0 ms) [ RUN ] GuestConfigParserTest.Memory_TooSmall [ERROR:garnet/bin/guest/vmm/guest_config.cc(245)] Requested memory 1024 is less than the minimum supported size 1048576 [ERROR:garnet/bin/guest/vmm/guest_config.cc(100)] Failed to parse option string '1k' usage: exe_name [OPTIONS] OPTIONS: --block=[spec] Adds a block device with the given parameters --cmdline-add=[string] Adds 'string' to the existing kernel command line. This will overwrite any existing command line created using --cmdline or --cmdline-add --cmdline=[string] Use 'string' as the kernel command line --cpus=[number] Number of virtual CPUs available to the guest --dtb-overlay=[path] Load a DTB overlay for a Linux kernel --host-memory Directly map host memory into the guest --linux=[path] Load a Linux kernel from 'path' --legacy-net Enable legacy virtio-net (uses host interface) --memory=[bytes] Allocate 'bytes' of memory for the guest. The suffixes 'k', 'M', and 'G' are accepted --interrupt=[spec] Adds a hardware interrupt mapping to the guest --ramdisk=[path] Load 'path' as an initial RAM disk --virtio-balloon Enable virtio-balloon (default) --virtio-console Enable virtio-console (default) --virtio-gpu Enable virtio-gpu and virtio-input (default) --virtio-net Enable virtio-net (default) --virtio-rng Enable virtio-rng (default) --virtio-vsock Enable virtio-vsock (default) --zircon=[path] Load a Zircon kernel from 'path' BLOCK SPEC Block devices can be specified by path: /pkg/data/disk.img Additional Options: rw/ro: Create a read/write or read-only device. fdio: Use the FDIO back-end for the block device. Ex: To open a filesystem resource packaged with the guest application (read-only is important here as the /pkg/data namespace provides read-only view into the package resources): /pkg/data/system.img,fdio,ro To specify a block device with a given path and read-write permissions /dev/class/block/000,fdio,rw [ OK ] GuestConfigParserTest.Memory_TooSmall (0 ms) [ RUN ] GuestConfigParserTest.Memory_IllegalModifier [ERROR:garnet/bin/guest/vmm/guest_config.cc(240)] Invalid size modifier l [ERROR:garnet/bin/guest/vmm/guest_config.cc(100)] Failed to parse option string '5l' usage: exe_name [OPTIONS] OPTIONS: --block=[spec] Adds a block device with the given parameters --cmdline-add=[string] Adds 'string' to the existing kernel command line. This will overwrite any existing command line created using --cmdline or --cmdline-add --cmdline=[string] Use 'string' as the kernel command line --cpus=[number] Number of virtual CPUs available to the guest --dtb-overlay=[path] Load a DTB overlay for a Linux kernel --host-memory Directly map host memory into the guest --linux=[path] Load a Linux kernel from 'path' --legacy-net Enable legacy virtio-net (uses host interface) --memory=[bytes] Allocate 'bytes' of memory for the guest. The suffixes 'k', 'M', and 'G' are accepted --interrupt=[spec] Adds a hardware interrupt mapping to the guest --ramdisk=[path] Load 'path' as an initial RAM disk --virtio-balloon Enable virtio-balloon (default) --virtio-console Enable virtio-console (default) --virtio-gpu Enable virtio-gpu and virtio-input (default) --virtio-net Enable virtio-net (default) --virtio-rng Enable virtio-rng (default) --virtio-vsock Enable virtio-vsock (default) --zircon=[path] Load a Zircon kernel from 'path' BLOCK SPEC Block devices can be specified by path: /pkg/data/disk.img Additional Options: rw/ro: Create a read/write or read-only device. fdio: Use the FDIO back-end for the block device. Ex: To open a filesystem resource packaged with the guest application (read-only is important here as the /pkg/data namespace provides read-only view into the package resources): /pkg/data/system.img,fdio,ro To specify a block device with a given path and read-write permissions /dev/class/block/000,fdio,rw [ OK ] GuestConfigParserTest.Memory_IllegalModifier (0 ms) [ RUN ] GuestConfigParserTest.Memory_NonNumber [ERROR:garnet/bin/guest/vmm/guest_config.cc(224)] Value is not a size string: abc [ERROR:garnet/bin/guest/vmm/guest_config.cc(100)] Failed to parse option string 'abc' usage: exe_name [OPTIONS] OPTIONS: --block=[spec] Adds a block device with the given parameters --cmdline-add=[string] Adds 'string' to the existing kernel command line. This will overwrite any existing command line created using --cmdline or --cmdline-add --cmdline=[string] Use 'string' as the kernel command line --cpus=[number] Number of virtual CPUs available to the guest --dtb-overlay=[path] Load a DTB overlay for a Linux kernel --host-memory Directly map host memory into the guest --linux=[path] Load a Linux kernel from 'path' --legacy-net Enable legacy virtio-net (uses host interface) --memory=[bytes] Allocate 'bytes' of memory for the guest. The suffixes 'k', 'M', and 'G' are accepted --interrupt=[spec] Adds a hardware interrupt mapping to the guest --ramdisk=[path] Load 'path' as an initial RAM disk --virtio-balloon Enable virtio-balloon (default) --virtio-console Enable virtio-console (default) --virtio-gpu Enable virtio-gpu and virtio-input (default) --virtio-net Enable virtio-net (default) --virtio-rng Enable virtio-rng (default) --virtio-vsock Enable virtio-vsock (default) --zircon=[path] Load a Zircon kernel from 'path' BLOCK SPEC Block devices can be specified by path: /pkg/data/disk.img Additional Options: rw/ro: Create a read/write or read-only device. fdio: Use the FDIO back-end for the block device. Ex: To open a filesystem resource packaged with the guest application (read-only is important here as the /pkg/data namespace provides read-only view into the package resources): /pkg/data/system.img,fdio,ro To specify a block device with a given path and read-write permissions /dev/class/block/000,fdio,rw [ OK ] GuestConfigParserTest.Memory_NonNumber (0 ms) [ RUN ] GuestConfigParserTest.VirtioGpu [ OK ] GuestConfigParserTest.VirtioGpu (0 ms) [----------] 21 tests from GuestConfigParserTest (2 ms total) [----------] Global test environment tear-down [==========] 21 tests from 1 test case ran. (2 ms total) [ PASSED ] 21 tests.