When KVM unit tests gets killed due to timeout, result.stdout
is empty and the test fails with "no results in stdout". In this
case it is useful to collect the logs from the "logs" directory
to debug the problem since we don't have any useful information
in stdout.
Signed-off-by: Anirudh Rayabharam <anrayabh@microsoft.com>
Increase timeout for Cloud Hypervisor tests since a lot of runs are
failing due to timeout errors.
Signed-off-by: Anirudh Rayabharam <anrayabh@microsoft.com>
Skip Cloud Hypervisor, libvirt, KVM tests for distributions other than
Ubuntu and CBLMariner. Lots of failures in other distros leading to
exceedingly high failure rate. Other distros can be enabled after fixing
these issues. Just to clarify: it is the implementation of these test
cases in LISA that doesn't currently support other distros. It is not
a limitation of the tests themselves.
Signed-off-by: Anirudh Rayabharam <anrayabh@microsoft.com>
For increased test reliability, we decided to reduce the bar for ring ping performance. Further discussion may need to occur surrounding the performance expectations of this test.
The error is benign as they indicate that the "cfg80211 wifi driver"
is not able to find its firmware. Given that there is no wifi device
on the Azure VM platform, it is safe to ignore this error message.
verify_boot_error_fail_warnings test fails on Mariner due to SGI XFS
log message displayed on bootup. Add log to whitelist as the log does
not indicate any failures.
This change makes parameters clearly, and reduce broken on arm only
parameters.
1. Add new AzureNodeArmParameter, which inherits from AzureNodeSchema.
Handle special initialize logic in the AzureNodeArmParameter.
2. Move arm parameter special values from AzureNodeSchema to
AzureNodeArmParameter.
3. Remove duplicate logic in _generate_min_capability.