~djacobs98/checkbox-iiotg/+git/checkbox-provider-intliotg:tsn_tests2

Last commit made on 2023-02-22
Get this branch:
git clone -b tsn_tests2 https://git.launchpad.net/~djacobs98/checkbox-iiotg/+git/checkbox-provider-intliotg
Only Doug Jacobs can upload to this branch. If you are Doug Jacobs please log in for upload directions.

Branch merges

Branch information

Recent commits

7568dbb... by Doug Jacobs

Initial check in. Add additional manual TSN tests and update the test plan. Work on automation later.

57dd6bc... by Ubuntu <email address hidden>

Merge #435625 from ~baconyao/checkbox-iiotg/+git/checkbox-provider-intliotg:fix-thermal

Modify: Append the CPU mode to blacklist

According to the support list of thermald, the EHL (mode:150) and the
ICL-D (mode: 108) are no supported by thermald.

We also check the thermald should be active in classic image and
inactive in core image

Please see:
  - https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L688

c71a505... by PeiYao Chang

Modify: Append the CPU mode to blacklist

According to the support list of thermald, the EHL (mode:150) and the
ICL-D (mode: 108) are no supported by thermald.

We also check the thermald should be active in classic image and
inactive in core image

Please see:
 - https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L688

a0f8449... by Ubuntu <email address hidden>

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

1fa7cdb... by PeiYao Chang

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 origianl logic of watchdog/detect for project image

0a920e3... by Ubuntu <email address hidden>

Merge #434531 from ~baconyao/checkbox-iiotg/+git/checkbox-provider-intliotg:fix-va-api

Change: Remove va-api plan from server and core

The va-api case is for testing the video acceleration and it shouldn't be
executed in Server and Core environment.

bbd58a9... by PeiYao Chang

Change: Remove va-api plan from server and core

The va-api case is for testing the video acceleration and it shouldn't be
executed in Server and Core environment.

30f0ff0... by Ubuntu <email address hidden>

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.

711c10b... by PeiYao Chang

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.

0fddf25... by Ubuntu <email address hidden>

Merge #431938 from ~zongminl/checkbox-iiotg/+git/checkbox-provider-intliotg:remove-original-test-plans

Change: Remove the original test plans since they have already been split into test plans for jammy and focal