From: "kernelci.org bot" <bot@kernelci.org>
To: rafael@kernel.org, linux-pm@vger.kernel.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: pm/testing sleep: 4 runs, 5 regressions (v5.16-rc8-173-g00759929cccb)
Date: Tue, 11 Jan 2022 21:39:30 -0800 (PST) [thread overview]
Message-ID: <61de6992.1c69fb81.62cde.19b0@mx.google.com> (raw)
pm/testing sleep: 4 runs, 5 regressions (v5.16-rc8-173-g00759929cccb)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
--------------------+------+---------------+----------+--------------------+------------
rk3288-rock2-square | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 5
Details: https://kernelci.org/test/job/pm/branch/testing/kernel/v5.16-rc8-173-g00759929cccb/plan/sleep/
Test: sleep
Tree: pm
Branch: testing
Describe: v5.16-rc8-173-g00759929cccb
URL: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
SHA: 00759929cccbf2e508326f2d9139ca708195d8f1
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
--------------------+------+---------------+----------+--------------------+------------
rk3288-rock2-square | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 5
Details: https://kernelci.org/test/plan/id/61de5c3047938d481eef676f
Results: 2 PASS, 16 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//pm/testing/v5.16-rc8-173-g00759929cccb/arm/multi_v7_defconfig/gcc-10/lab-collabora/sleep-rk3288-rock2-square.txt
HTML log: https://storage.kernelci.org//pm/testing/v5.16-rc8-173-g00759929cccb/arm/multi_v7_defconfig/gcc-10/lab-collabora/sleep-rk3288-rock2-square.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye/20211224.1/armhf/rootfs.cpio.gz
* sleep.rtcwake-mem-5: https://kernelci.org/test/case/id/61de5c3047938d481eef677c
new failure (last pass: v5.16-rc8-171-gf099fd60c342)
* sleep.rtcwake-mem-4: https://kernelci.org/test/case/id/61de5c3047938d481eef677d
new failure (last pass: v5.16-rc8-171-gf099fd60c342)
2022-01-12T04:42:11.551880 rtcwake: ass<4>[ 14.779011] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-01-12T04:42:11.552236 uming RTC uses UTC ...
2022-01-12T04:42:11.597129 rtcwake: read rtc time failed: Invalid a<4>[ 14.798591] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-01-12T04:42:11.597658 rgument
2022-01-12T04:42:11.598527 rtcwake: assuming RTC uses UTC ...
2022-01-12T04:42:11.598908 rtcwake: read rtc ti<4>[ 14.813278] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-01-12T04:42:11.599280 me failed: Invalid argument
* sleep.rtcwake-mem-3: https://kernelci.org/test/case/id/61de5c3047938d481eef677e
new failure (last pass: v5.16-rc8-171-gf099fd60c342)
* sleep.rtcwake-mem-2: https://kernelci.org/test/case/id/61de5c3047938d481eef677f
new failure (last pass: v5.16-rc8-171-gf099fd60c342)
2022-01-12T04:42:11.504813 rtcwake: assuming RTC uses UTC ...
2022-01-12T04:42:11.548958 rtcwake: read rt<4>[ 14.739837] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-01-12T04:42:11.549515 c time failed: Invalid argument
2022-01-12T04:42:11.550414 rtcwake: assuming RTC uses UTC .<4>[ 14.758687] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-01-12T04:42:11.550798 ..
2022-01-12T04:42:11.551167 rtcwake: read rtc time failed: Invalid argument
* sleep.rtcwake-mem-1: https://kernelci.org/test/case/id/61de5c3047938d481eef6780
new failure (last pass: v5.16-rc8-171-gf099fd60c342)
reply other threads:[~2022-01-12 5:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61de6992.1c69fb81.62cde.19b0@mx.google.com \
--to=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).