| Age | Commit message (Collapse) | Author |
| LP: #1937257 |
| exit takes only integer args in the range 0 - 255 If we return the taint value read from /proc/sys/kernel/tainted, it might exceed this range and causing unexpected behaviour. e.g. on a system with kernel warning $ ./kernel_taint_test.py Kernel taint value is 512 Taint bit value: 9 (kernel issued warning) Taint bit value: 9 (kernel issued warning) $ echo $? 0 Let's just simplify the return logic of report_failures() to return either 0 or 1. |
| exit takes only integer args in the range 0 - 255 If we return the taint value read from /proc/sys/kernel/tainted, it might exceed this range and causing unexpected behaviour. e.g. on a system with kernel warning $ ./kernel_taint_test.py Kernel taint value is 512 Taint bit value: 9 (kernel issued warning) Taint bit value: 9 (kernel issued warning) $ echo $? 0 Let's just simplify the return logic of report_failures() to return either 0 or 1. Signed-off-by: Po-Hsu Lin <po-hsu.lin@canonical.com> |
| ~zongminl/plainbox-provider-checkbox:sync-watchdog-test-between-classic-and-core Change: Align the test for watchdog config on classic and core image Watchdog implementation on both classic and core image no longer rely on watchdogd service since 20.04, with this change watchdog/systemd-config tests only systemd configuration on 20.04 and later series while keeping the original test for prior releases |
| Watchdog implementation on both classic and core image no longer rely on watchdogd service since 20.04, with this change watchdog/systemd-config tests only systemd configuration on 20.04 and later series while keeping the original test for prior releases |
| ~kchsieh/plainbox-provider-checkbox/+git/plainbox-provider-checkbox:iwlwifi-microcode-crash Add: iwlwifi microcode crash check |
| LP: #1932548 |
| Release_2021_Week28 |
| |
| |
| ~bladernr/plainbox-provider-checkbox:rm-efiboot-test-regression |
| old systems we know aren't booting EFI mode |
| |
| ~narahuang/plainbox-provider-checkbox/+git/plainbox-provider-checkbox:kernel-failboot-test |
| |
| |
| |
| |
| |
| not set to 'dangerous' |
| ~kissiel/plainbox-provider-checkbox:fix-1933632-bad-timestamps |
| ~bladernr/plainbox-provider-checkbox:1908129-dont-fail-taint-check-zfs |
| Previously, when the buildstamp job ran on core and wasn't able to get an actual information about the buildstamp it printed nothing and returned 0, making the tar exporter choke on empty array of lines. This patch ensures that the job either yields some info or fais. Fixes LP: #1933632 |
| |
| ~bladernr/plainbox-provider-checkbox:1917365-sosreport-deprecated-command |
| |
| |
| Means this data is removed from the session share when the test is finished running. |
| Fix problem with distribution codenames in virtualization test |
| |
| Compatibility with uc20 FDE functionality will now be tested using FWTS |
| |
| ~zongminl/plainbox-provider-checkbox:fix-required-bootstrap-serial-automated unit/serial: fix the necessary bootstrap missing in serial-automated plan |
| |
| |
| |
| |
| Currently requires that snap providing the uvtool executables have been installed from a suitable snap and the apps aliased such that there is no snap name prefix |
| ~kchsieh/plainbox-provider-checkbox/+git/plainbox-provider-checkbox:short-idle-check Add: check package cstate during short idle |
| expect to be there lp: #1908129 |
| |
| In rare cases the version of cryptsetup in the checkbox snap will not match that used to creation the encrypted partition. In such cases the type will appear as `n/a` and the regex will not match. Relax the test to handle this situation. |
| ~iamerin-c/plainbox-provider-checkbox/+git/plainbox-provider-checkbox:touchscreen_drag-n-drop Update touchscreen/drag-and-drop test description |
| |
| Fixes: lp:1903264 |
| |
| LP: #1928053 According to Intel blog [1], the system can reach at least PC8 when screen on. The test job check if the device can reach PC8 during idle screen on. For platform has no PC8, the target shoule be as deeper as possible. [1] https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting |
| |
| When running iperf tests the network.py test turned off interfaces other than the one in test. This caused two probems. First, some systems have interfaces that cannot or should not be disabled. Second, if the test crashed or has been stopped while testing it made the system cut off from the network. |
| Ethernet test plans lacked the bootstrapping section which made them not generate the included jobs. This patch adds bootstrapping sections. |