/usr/lib/plainbox-providers-1/checkbox/jobs/miscellanea.txt is in plainbox-provider-checkbox 0.3-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 | plugin: shell
name: miscellanea/submission-resources
depends: cpuinfo dpkg lsb package uname
estimated_duration: 1.0
command: true
description:
A meta-job depending on the resources needed for a valid submission.
plugin: manual
name: miscellanea/tester-info
description:
PURPOSE:
Keep tester related information in the report
STEPS:
1. Tester Information
2. Please enter the following information in the comments field:
a. Name
b. Email Address
c. Reason for this test run
VERIFICATION:
Nothing to verify for this test
plugin: user-interact-verify
name: miscellanea/chvt
requires:
package.name == 'kbd'
user: root
command: cycle_vts
description:
PURPOSE:
This test will check that the system can switch to a virtual terminal and back to X
STEPS:
1. Click "Test" to switch to another virtual terminal and then back to X
VERIFICATION:
Did your screen change temporarily to a text console and then switch back to your current session?
plugin: shell
name: miscellanea/fwts_test
requires:
package.name == 'fwts'
user: root
description:
Run Firmware Test Suite (fwts) automated tests.
environ: CHECKBOX_DATA
command:
fwts_test -l $CHECKBOX_DATA/fwts_results.log
plugin: attachment
name: miscellanea/fwts_results.log
command:
[[ -e ${CHECKBOX_DATA}/fwts_results.log ]] && cat ${CHECKBOX_DATA}/fwts_results.log
description: Attaches the FWTS results log to the submission
plugin: shell
name: miscellanea/ipmi_test
requires: package.name == 'ipmitool'
user: root
command: ipmi_test
description:
This will run some basic connectivity tests against a BMC, verifying that IPMI works.
plugin: shell
name: miscellanea/is_laptop
user: root
description:
Determine if we need to run tests specific to portable computers that may not apply to desktops.
command: check_is_laptop
plugin: shell
name: miscellanea/apport-directory
requires: package.name == 'apport'
command: if [ -d /var/crash ]; then if [ $(find /var/crash -type f | grep -v .lock | wc -l) -eq 0 ]; then echo "/var/crash is empty"; else echo `ls /var/crash`; false; fi; else echo "/var/crash does not exist"; fi
description:
Test that the /var/crash directory doesn't contain anything. Lists the files contained within if it does, or echoes the status of the directory (doesn't exist/is empty)
plugin: shell
name: miscellanea/sources-list
command: sources_test $SOURCES_LIST "$REPOSITORIES"
description: Checks that a specified sources list file contains the requested repositories
plugin: local
name: miscellanea/pxe_boot
requires: device.category == 'NETWORK'
description: Automated job to generate the PXE verification test for each NIC.
command:
cat <<'EOF' | run_templates -s 'udev_resource | filter_templates -w "category=NETWORK" | awk "/path: / { print \$2 }" | xargs -n 1 sh -c "for i in \`ls /sys\$0/net 2>/dev/null\`; do echo \$0 \$i; done"'
plugin: manual
name: miscellanea/pxe_boot_$2
description:
PURPOSE:
This test will verify that you have attempted to PXE boot this machine from
the network device $2.
STEPS:
1. Prior to running this test, you should have attempted to boot this system via PXE on every Network Port available.
VERIFICATION:
1. Select Yes if you successfully used PXE boot this system using the NIC $2
2. Select No if you did not attempt to PXE boot this system using the NIC $2
3. Select No if you attempted to PXE boot via $2 and it failed for some reason.
EOF
plugin: local
name: miscellanea/remote_shared_ipmi
requires: device.category == 'NETWORK'
description: Automated job to generate the Remote Shared IPMI verification test for each NIC.
command:
cat <<'EOF' | run_templates -s 'udev_resource | filter_templates -w "category=NETWORK" | awk "/path: / { print \$2 }" | xargs -n 1 sh -c "for i in \`ls /sys\$0/net 2>/dev/null\`; do echo \$0 \$i; done"'
plugin: manual
name: miscellanea/remote_shared_ipmi_$2
description:
PURPOSE:
This test will verify that you have attempted IPMI control of this machine from the network device $2.
STEPS:
1. Prior to running this test, you should have configured and used IPMI to power this machine off and on using every Network Port available.
VERIFICATION:
1. Select Yes if you successfully used IPMI to remotely power this system off and on using the NIC $2
2. Select No if you did not attempt to use IPMI to remotely power this sytem off and on via the NIC $2
3. Select No if you attempted to use IPMI to remotely power off/on this system via $2 and it failed for some reason.
EOF
plugin: manual
name: miscellanea/remote_dedicated_ipmi
description:
PURPOSE:
Some systems do not share IPMI over all NICs but instead have a dedicated management port directly connected to the BMC. This test verifies that you have used that port for remote IPMI connections and actions.
STEPS:
1. Prior to running the test, you should have configured and used the Dedicated Management Port to remotely power off/on this sytem.
VERIFICATION:
Skip this test if this system ONLY uses shared management/ethernet ports OR if this system does not have a BMC (Management Console)
1. Select Yes if you successfully used IPMI to remotely power this system off and on using the dedicated management port.
2. Select No if you attempted to use the dedicated management port to remotely power this system off/on and it failed for some reason.
|