Merge ~artur-at-work/plainbox-provider-pc-sanity:update-hyperlink-to-s0ix-manual into plainbox-provider-pc-sanity:master

[Artur Pak]

Update the link to linux-s0ix-troubleshooting page (JIRA: OEX86-84)

[OEM Taipei Bot (oem-taipei-bot)]

[autopkgtest]
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

https://oem-share.canonical.com/partners/lyoncore/share/artifacts/plainbox-provider-pc-sanity/plainbox-provider-pc-sanity-1.0.2-81b14a1-in-linux-container-jammy

[Dirk Su (dirksu)]

LGTM

review: Approve

[Andy Chi (andch)]

Can we trigger the test again?

[Artur Pak (artur-at-work)]

> Can we trigger the test again?

OK, I made changes to second manual's link and uploaded again.

[OEM Taipei Bot (oem-taipei-bot)]

[autopkgtest]
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

https://oem-share.canonical.com/partners/lyoncore/share/artifacts/plainbox-provider-pc-sanity/plainbox-provider-pc-sanity-1.0.2-a4c2aa1-in-linux-container-jammy

[Artur Pak (artur-at-work)]

It's probably failing due to outdated ppa for checkbox:
https://launchpad.net/~checkbox-dev/+archive/ubuntu/ppa

I'll try to update to new ppa:
https://launchpad.net/~checkbox-dev/+archive/ubuntu/edge

---error while building:
The following packages have unmet dependencies:
 17s autopkgtest-satdep : Depends: python3-checkbox-ng but it is not installable
 17s Depends: checkbox-provider-certification-client but it is not installable
 17s Depends: checkbox-provider-base but it is not installable
 17s E: Unable to correct problems, you have held broken packages.
 17s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs
 17s blame: .
 17s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
 17s autopkgtest [10:08:21]: ERROR: erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

[OEM Taipei Bot (oem-taipei-bot)]

[autopkgtest]
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

https://oem-share.canonical.com/partners/lyoncore/share/artifacts/plainbox-provider-pc-sanity/plainbox-provider-pc-sanity-1.0.2-b2ebb7c-in-linux-container-jammy

[Andy Chi (andch)]

Artur,
Is it necessary to use checkbox-dev/edge? Maybe checkbox-dev/beta?

[OEM Taipei Bot (oem-taipei-bot)]

[autopkgtest]
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

https://oem-share.canonical.com/partners/lyoncore/share/artifacts/plainbox-provider-pc-sanity/plainbox-provider-pc-sanity-1.0.2-b2ebb7c-in-linux-container-jammy

[Artur Pak (artur-at-work)]

> Artur,
> Is it necessary to use checkbox-dev/edge? Maybe checkbox-dev/beta?

Thanks, yes, switched to beta instead.

[OEM Taipei Bot (oem-taipei-bot)]

[autopkgtest]
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

https://oem-share.canonical.com/partners/lyoncore/share/artifacts/plainbox-provider-pc-sanity/plainbox-provider-pc-sanity-1.0.2-f4ece88-in-linux-container-jammy

[OEM Taipei Bot (oem-taipei-bot)]

[autopkgtest]
help FAIL badpkg
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
checkbox-cli-list FAIL badpkg
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
bootstrap-pc-sanity FAIL badpkg
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
cvescan FAIL badpkg
blame: .
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

https://oem-share.canonical.com/partners/lyoncore/share/artifacts/plainbox-provider-pc-sanity/plainbox-provider-pc-sanity-1.0.2-f4ece88-in-linux-container-jammy

[Artur Pak (artur-at-work)]

"prepare-checkbox-sanity" is missing in beta channel:
https://launchpad.net/~checkbox-dev/+archive/ubuntu/beta

[OEM Taipei Bot (oem-taipei-bot)]

[autopkgtest]
help PASS
checkbox-cli-list PASS
bootstrap-pc-sanity PASS
cvescan PASS

https://oem-share.canonical.com/partners/lyoncore/share/artifacts/plainbox-provider-pc-sanity/plainbox-provider-pc-sanity-1.0.2-f4ece88-in-linux-container-jammy

[Artur Pak (artur-at-work)]

Hi Andy,
 Could you help to review please?

 It now can pass the autopkgtest after adding prepare-checkbox-sanity to beta and increasing CI job timeout.

[Andy Chi (andch)]

LGTM. Thanks

review: Approve

diff --git a/README.md b/README.md
index cf8ac08..df5e0bb 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 This provider contains test cases and a test plan for pc sanity testing.
 
-It depends on packages from ppa:checkbox-dev/ppa in build time.
+It depends on packages from ppa:checkbox-dev/beta in build time.
 The launchpad recipe build it daily : https://code.launchpad.net/~oem-solutions-engineers/+recipe/plainbox-provider-pc-sanity-daily-1
 
 ## Run autopkgtest to check build time and installation time sanity.
diff --git a/autopkgtest.sh b/autopkgtest.sh
index 3d8737d..286bee7 100755
--- a/autopkgtest.sh
+++ b/autopkgtest.sh
@@ -3,5 +3,5 @@
 if [ "build" = "$1" ]; then
     autopkgtest-build-lxd images:ubuntu/focal/amd64
 else
-    autopkgtest -U --setup-commands="sudo apt-get install -y wget snapd software-properties-common &&  add-apt-repository -y -u -s ppa:checkbox-dev/ppa && export DEBIAN_FRONTEND=noninteractive"  --shell-fail -- lxd autopkgtest/ubuntu/focal/amd64
+    autopkgtest -U --setup-commands="sudo apt-get install -y wget snapd software-properties-common &&  add-apt-repository -y -u -s ppa:checkbox-dev/beta && export DEBIAN_FRONTEND=noninteractive"  --shell-fail -- lxd autopkgtest/ubuntu/focal/amd64
 fi
diff --git a/bin/autopkgtest-plainbox-provider-pc-sanity-auto b/bin/autopkgtest-plainbox-provider-pc-sanity-auto
index a7bfb37..4d06369 100755
--- a/bin/autopkgtest-plainbox-provider-pc-sanity-auto
+++ b/bin/autopkgtest-plainbox-provider-pc-sanity-auto
@@ -11,4 +11,4 @@ if ! valid_oem_scripts_config; then
     exit 1
 fi
 
-autopkgtest-collect-credentials ppa:checkbox-dev/ppa "$@"
+autopkgtest-collect-credentials ppa:checkbox-dev/beta "$@"
diff --git a/bin/check-turbostat-power-residency.sh b/bin/check-turbostat-power-residency.sh
index ffdc02b..2d6d7f8 100755
--- a/bin/check-turbostat-power-residency.sh
+++ b/bin/check-turbostat-power-residency.sh
@@ -1,6 +1,6 @@
 #!/bin/bash
 
-#refer to https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting
+#refer to https://web.archive.org/web/20230614200306/https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting
 set -e
 state="pass"
 command -v turbostat || exit 1
@@ -100,7 +100,7 @@ if [ "$state" != "pass" ]; then
     echo "Otherwise, please get PHM report to check which device blocking PC10 or s0ix and open bugs for HWE to check kernel modules"
     echo ""
     echo "reference:"
-    echo " - https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting"
-    echo " - https://01.org/blogs/qwang59/2018/how-achieve-s0ix-states-linux"
+    echo " - https://web.archive.org/web/20230614200306/https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting"
+    echo " - https://blog.csdn.net/yuzaipiaofei/article/details/90384456"
     exit 1
 fi
diff --git a/units/pc-sanity/pc-sanity-check-devices.pxu b/units/pc-sanity/pc-sanity-check-devices.pxu
index c5511f9..ecc2028 100644
--- a/units/pc-sanity/pc-sanity-check-devices.pxu
+++ b/units/pc-sanity/pc-sanity-check-devices.pxu
@@ -78,7 +78,7 @@ command:
  if [ ! -d /sys/kernel/debug/pmc_core ]; then
      echo "The system has no /sys/kernel/debug/pmc_core."
      echo "It is required for doing low power idle analysis."
-     echo "For more detail, please refer to https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting"
+     echo "For more detail, please refer to https://web.archive.org/web/20230614200306/https://01.org/blogs/qwang59/2020/linux-s0ix-troubleshooting"
      exit 1
  fi
 _summary: Check if intel_pmc_core driver is probed