Merge #434914 from ~baconyao/checkbox-iiotg/+git/checkbox-provider-intliotg:fix-watchdog
Change: Redesign the watchdog test plan
Redesign the watchdog test plan in order to cover the more generic
scenario, therefore, I exclude all of the genereic watchdog cases and
use the new designed flow.
For an image, there are four combinations based on the source and
type. There are two sources, stock and oem, and two types, classic
and core.
The differences between stock and oem image is the value of
RuntimeWatchdogSec is 0 in stock but should not be 0 in oem image.
For stock classic image, we have to probe the module of watchdog by
ourself via the WATCHDOG_TYPE variable in config. As for core image,
the module is loaded automatically, however, we still need to check
its identity because it might be the wrong moudle if the BIOS setting
is wrong.
The following files are migrating from generic checkbox, so no need to be reviewed
- failed_service_check.sh
- for watchdog/general/post-trigger-system-reset-auto only
- udev_resource.py
- for watchdog/general/detect
- I keep the original logic of watchdog/detect for project image
Redesign the watchdog test plan in order to cover the more generic
scenario, therefore, I exclude all of the genereic watchdog cases and
use the new designed flow.
For an image, there are four combinations based on the source and
type. There are two sources, stock and oem, and two types, classic
and core.
The differences between stock and oem image is the value of
RuntimeWatchdogSec is 0 in stock but should not be 0 in oem image.
For stock classic image, we have to probe the module of watchdog by
ourself via the WATCHDOG_TYPE variable in config. As for core image,
the module is loaded automatically, however, we still need to check
its identity because it might be the wrong moudle if the BIOS setting
is wrong.
The following files are migrating from generic checkbox, so no need to be reviewed
- failed_service_check.sh
- for watchdog/general/post-trigger-system-reset-auto only
- udev_resource.py
- for watchdog/general/detect
- I keep the origianl logic of watchdog/detect for project image
Merge #433841 from ~baconyao/checkbox-iiotg/+git/checkbox-provider-intliotg:redesign-dwc3-case
Fix: redesign the DWC3 test cases
In this new flow, the cases 'driver-detect' and 'driver-module'
depend on the value 'has_usb_dwc3_controller' from manifest.json only.
Once tester marks Yes in manifest, these two cases will be executed and
check the driver and module should be loaded.
The reason why I remove the 'fail-on-resource' flag is because I
observed its priority is higher than 'depends'. This truth causes some
jobs still be failed even they depend on manifest and the value is 'no'
in manifest.
In this new flow, the cases 'driver-detect' and 'driver-module'
depend on the value 'has_usb_dwc3_controller' from manifest.json only.
Once tester marks Yes in manifest, these two cases will be executed and
check the driver and module should be loaded.
The reason why I remove the 'fail-on-resource' flag is because I
observed its priority is higher than 'depends'. This truth causes some
jobs still be failed even they depend on manifest and the value is 'no'
in manifest.