Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/master sleep: 5 runs, 3 regressions (renesas-devel-2021-10-11-v5.15-rc5)
Date: Tue, 12 Oct 2021 10:33:25 -0700 (PDT)	[thread overview]
Message-ID: <6165c6e5.1c69fb81.25209.10a7@mx.google.com> (raw)

renesas/master sleep: 5 runs, 3 regressions (renesas-devel-2021-10-11-v5.15-rc5)

Regressions Summary
-------------------

platform            | arch | lab           | compiler | defconfig          | regressions
--------------------+------+---------------+----------+--------------------+------------
rk3288-rock2-square | arm  | lab-collabora | gcc-8    | multi_v7_defconfig | 3          

  Details:  https://kernelci.org/test/job/renesas/branch/master/kernel/renesas-devel-2021-10-11-v5.15-rc5/plan/sleep/

  Test:     sleep
  Tree:     renesas
  Branch:   master
  Describe: renesas-devel-2021-10-11-v5.15-rc5
  URL:      https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
  SHA:      6e602e69ec04a3e0887e4fd9189250b4e7ee7e23 


Test Regressions
---------------- 


platform            | arch | lab           | compiler | defconfig          | regressions
--------------------+------+---------------+----------+--------------------+------------
rk3288-rock2-square | arm  | lab-collabora | gcc-8    | multi_v7_defconfig | 3          

  Details:     https://kernelci.org/test/plan/id/6165abb74f445e127d08fade

  Results:     2 PASS, 12 FAIL, 0 SKIP
  Full config: multi_v7_defconfig
  Compiler:    gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
  Plain log:   https://storage.kernelci.org//renesas/master/renesas-devel-2021-10-11-v5.15-rc5/arm/multi_v7_defconfig/gcc-8/lab-collabora/sleep-rk3288-rock2-square.txt
  HTML log:    https://storage.kernelci.org//renesas/master/renesas-devel-2021-10-11-v5.15-rc5/arm/multi_v7_defconfig/gcc-8/lab-collabora/sleep-rk3288-rock2-square.html
  Rootfs:      http://storage.kernelci.org/images/rootfs/debian/buster/20211008.0/armhf/rootfs.cpio.gz 


  * sleep.rtcwake-mem-5: https://kernelci.org/test/case/id/6165abb74f445e127d08fae9
        new failure (last pass: renesas-devel-2021-10-08-v5.15-rc4)

    2021-10-12T15:37:22.613108  rtcwake: assuming RTC uses UTC ...
    2021-10-12T15:37:22.658756  <4>[   14.439956] rtc-hym8563 0-0051: no valid clock/calendar values available
    2021-10-12T15:37:22.659113  rtcwake: read rtc time failed: Invalid argument
    2021-10-12T15:37:22.659658  rtcwake: assumin<4>[   14.460750] rtc-hym8563 0-0051: no valid clock/calendar values available
    2021-10-12T15:37:22.659911  g RTC uses UTC ...
    2021-10-12T15:37:22.660154  rtcwake: read rtc time failed: Invalid argument   

  * sleep.rtcwake-mem-4: https://kernelci.org/test/case/id/6165abb74f445e127d08faea
        new failure (last pass: renesas-devel-2021-10-08-v5.15-rc4)

    2021-10-12T15:37:22.521622  SULT=pass>
    2021-10-12T15:37:22.562334  rtcwake: assuming RTC uses UTC ...
    2021-10-12T15:37:22.562609  rtcwake: read rtc time failed: Invalid argument
    2021-10-12T15:37:22.563034  _ID=rtcwake-mem-1 RESULT=fail>
    2021-10-12T15:37:22.563229  rtcwake: assuming RTC uses UTC ...
    2021-10-12T15:37:22.563420  rtcwake: read rtc time failed: Invalid argument
    2021-10-12T15:37:22.563802  L_TESTCASE TEST_CASE_ID=rtcwake-mem-2 RESULT=fail>
    2021-10-12T15:37:22.563985  rtcwake: assuming RTC uses UTC ...
    2021-10-12T15:37:22.610740  rtcwake: read rtc time failed: Invalid a<4>[   14.400648] rtc-hym8563 0-0051: no valid clock/calendar values available
    2021-10-12T15:37:22.611165  rgument 
    ... (3 line(s) more)  

  * sleep.rtcwake-mem-3: https://kernelci.org/test/case/id/6165abb74f445e127d08faeb
        new failure (last pass: renesas-devel-2021-10-08-v5.15-rc4) 
  

                 reply	other threads:[~2021-10-12 17:33 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=6165c6e5.1c69fb81.25209.10a7@mx.google.com \
    --to=bot@kernelci.org \
    --cc=kernelci-results@groups.io \
    --cc=linux-renesas-soc@vger.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