testing/igt: Add 2 more troubleshooting fixes.
Add fix for Running Tasts on DUT is failing: DUT software features.
Add fix for [Google-only] Building to Skylab DUT is failing: context
deadline exceeded.
BUG=b:181033521,b:186556348
TEST=N/A
Change-Id: I9a2e0e9e6b20d47682d3d8b21e4edeab4846330b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/docs/+/2884140
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Mark Yacoub <markyacoub@google.com>
Commit-Queue: Mark Yacoub <markyacoub@google.com>
diff --git a/testing/igt.md b/testing/igt.md
index aee9222..31bd82d 100644
--- a/testing/igt.md
+++ b/testing/igt.md
@@ -102,7 +102,7 @@
b. You could be deploying to the wrong place.
Make sure you append `--root /usr/local` to `(outside)$ cros_sdk cros deploy <DUT IP> igt-gpu-tools`
-2. ### Deploying to DUT is failing
+2. ### Deploying to DUT is failing: Missing deps
a. You could be missing some dependencies.
For starters, do `(outside)$ cros_sdk emerge-$BOARD json-c mako markupsafe`
@@ -141,7 +141,29 @@
(outside)$ cros_sdk emerge-${BOARD} dev-libs/json-c && cros_sdk cros deploy <DUT IP> dev-libs/json-c
```
-3. ### If the test isn't starting on the DUT
+3. ### Running Tasts on DUT is failing: DUT software features
+If your DUT is missing software features and your error message looks like:
+```
+2021-05-07T17:43:11.013594Z Building local_test_runner, cros, remote_test_runner, cros
+2021-05-07T17:43:11.821523Z Built in 808ms
+2021-05-07T17:43:11.821585Z Pushing executables to target
+2021-05-07T17:43:12.045178Z Pushed executables in 224ms (sent 0 B)
+2021-05-07T17:43:12.870143Z Failed to run tests: failed to get DUT software features: can't check test deps; no software features reported by DUT
+```
+For debugging, it is legitimate to override tast with this option (`-checktestdeps=false`) as your stateful partition might be in a bad state. To fix, do
+```
+(outside)$ cros_sdk tast run -checktestdeps=false <DUT_IP> graphics.IGT.kms_*
+```
+
+4. ### [Google-only] Building to Skylab DUT is failing: context deadline exceeded
+if you can't connect to your *Skylab* DUT and your error looks like
+```
+2021-05-07T17:39:07.908035Z Connecting to skylab.cros
+2021-05-07T17:39:17.908447Z Failed to connect to skylab.cros: context deadline exceeded
+```
+Make sure you have the right [ProxyCommand](https://g3doc.corp.google.com/company/teams/cloudtop/faq.md?cl=head#ssh) in place and this [workaround](https://groups.google.com/a/google.com/g/chromeos-chatty-eng/c/opC-HyMTe8E/m/UkIi7diBCAAJ) to enable skylab from chroot.
+
+5. ### If the test isn't starting on the DUT
Make sure the UI is stopped on your DUT by doing `(device)$ stop ui`
---------------------------------------