linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/for-next baseline: 119 runs, 2 regressions (v5.10-rc1-11-g50afb29ae413)
Date: Thu, 29 Oct 2020 11:27:15 -0700 (PDT)	[thread overview]
Message-ID: <5f9b0983.1c69fb81.fba2f.8c9e@mx.google.com> (raw)

linusw/for-next baseline: 119 runs, 2 regressions (v5.10-rc1-11-g50afb29ae413)

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

platform        | arch  | lab           | compiler | defconfig          | regressions
----------------+-------+---------------+----------+--------------------+------------
bcm2837-rpi-3-b | arm64 | lab-baylibre  | gcc-8    | defconfig          | 1          
panda           | arm   | lab-collabora | gcc-8    | multi_v7_defconfig | 1          

  Details:  https://kernelci.org/test/job/linusw/branch/for-next/kernel/v5.10-rc1-11-g50afb29ae413/plan/baseline/

  Test:     baseline
  Tree:     linusw
  Branch:   for-next
  Describe: v5.10-rc1-11-g50afb29ae413
  URL:      https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
  SHA:      50afb29ae41368d750cf46bece2b13065b0e9cef 


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


platform        | arch  | lab           | compiler | defconfig          | regressions
----------------+-------+---------------+----------+--------------------+------------
bcm2837-rpi-3-b | arm64 | lab-baylibre  | gcc-8    | defconfig          | 1          

  Details:     https://kernelci.org/test/plan/id/5f9afd9db4dcfac8ee381020

  Results:     4 PASS, 1 FAIL, 0 SKIP
  Full config: defconfig
  Compiler:    gcc-8 (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0)
  Plain log:   https://storage.kernelci.org//linusw/for-next/v5.10-rc1-11-g50afb29ae413/arm64/defconfig/gcc-8/lab-baylibre/baseline-bcm2837-rpi-3-b.txt
  HTML log:    https://storage.kernelci.org//linusw/for-next/v5.10-rc1-11-g50afb29ae413/arm64/defconfig/gcc-8/lab-baylibre/baseline-bcm2837-rpi-3-b.html
  Rootfs:      http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-4-g97706c5d9567/arm64/baseline/rootfs.cpio.gz 


  * baseline.dmesg.crit: https://kernelci.org/test/case/id/5f9afd9db4dcfac8ee381025
        failing since 20 days (last pass: v5.9-rc8-78-g24160a8f7f13, first fail: v5.9-rc8-79-g3d6e8262d3c0)
        1 lines

    2020-10-29 17:34:23.036000+00:00  Connected to bcm2837-rpi-3-b console [channel connected] (~$quit to exit)
    2020-10-29 17:34:23.036000+00:00  (user:khilman) is already connected
    2020-10-29 17:34:37.899000+00:00  \0
    2020-10-29 17:34:37.900000+00:00  
    2020-10-29 17:34:37.900000+00:00  U-Boot 2018.11 (Dec 04 2018 - 10:54:32 -0800)
    2020-10-29 17:34:37.900000+00:00  
    2020-10-29 17:34:37.900000+00:00  DRAM:  948 MiB
    2020-10-29 17:34:37.915000+00:00  RPI 3 Model B (0xa02082)
    2020-10-29 17:34:38.002000+00:00  MMC:   mmc@7e202000: 0, sdhci@7e300000: 1
    2020-10-29 17:34:38.034000+00:00  Loading Environment from FAT... *** Warning - bad CRC, using default environment 
    ... (380 line(s) more)  
 


platform        | arch  | lab           | compiler | defconfig          | regressions
----------------+-------+---------------+----------+--------------------+------------
panda           | arm   | lab-collabora | gcc-8    | multi_v7_defconfig | 1          

  Details:     https://kernelci.org/test/plan/id/5f9aff7515a7e05cbf381035

  Results:     4 PASS, 1 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//linusw/for-next/v5.10-rc1-11-g50afb29ae413/arm/multi_v7_defconfig/gcc-8/lab-collabora/baseline-panda.txt
  HTML log:    https://storage.kernelci.org//linusw/for-next/v5.10-rc1-11-g50afb29ae413/arm/multi_v7_defconfig/gcc-8/lab-collabora/baseline-panda.html
  Rootfs:      http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-4-g97706c5d9567/armel/baseline/rootfs.cpio.gz 


  * baseline.dmesg.alert: https://kernelci.org/test/case/id/5f9aff7515a7e05cbf38103b
        failing since 62 days (last pass: gpio-v5.8-2-103-g22cc422070d9, first fail: v5.8-11991-gfc80c51fd4b2)
        60 lines

    2020-10-29 17:44:15.248000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c802
    2020-10-29 17:44:15.253000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c803
    2020-10-29 17:44:15.259000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c804
    2020-10-29 17:44:15.265000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c805
    2020-10-29 17:44:15.271000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c806
    2020-10-29 17:44:15.277000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c807
    2020-10-29 17:44:15.283000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c808
    2020-10-29 17:44:15.289000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c809
    2020-10-29 17:44:15.295000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c80a
    2020-10-29 17:44:15.301000+00:00  kern  :alert : BUG: Bad page state in process swapper/0  pfn:9c80b 
    ... (49 line(s) more)  
  

                 reply	other threads:[~2020-10-29 18:27 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=5f9b0983.1c69fb81.fba2f.8c9e@mx.google.com \
    --to=bot@kernelci.org \
    --cc=fellows@kernelci.org \
    --cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).