Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 245 boots: 19 failed, 219 passed with 4 offline, 3 untried/unknown (next-20200521)
Date: Fri, 22 May 2020 09:26:04 -0700 (PDT)
Message-ID: <5ec7fd1c.1c69fb81.c24e4.177f@mx.google.com> (raw)

******************************************
* WARNING: Boot tests are now deprecated *
******************************************

As kernelci.org is expanding its functional testing capabilities, the concept
of boot testing is now deprecated.  Boot results are scheduled to be dropped on
*5th June 2020*.  The full schedule for boot tests deprecation is available on
this GitHub issue: https://github.com/kernelci/kernelci-backend/issues/238

The new equivalent is the *baseline* test suite which also runs sanity checks
using dmesg and bootrr: https://github.com/kernelci/bootrr

See the *baseline results for this kernel revision* on this page:
https://kernelci.org/test/job/next/branch/master/kernel/next-20200521/plan/baseline/

-------------------------------------------------------------------------------

next/master boot: 245 boots: 19 failed, 219 passed with 4 offline, 3 untried/unknown (next-20200521)

Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200521/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200521/

Tree: next
Branch: master
Git Describe: next-20200521
Git Commit: e8f3274774b45b5f4e9e3d5cad7ff9f43ae3add5
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 103 unique boards, 26 SoC families, 30 builds out of 222

Boot Regressions Detected:

arm:

    sama5_defconfig:
        gcc-8:
          at91-sama5d4_xplained:
              lab-baylibre: failing since 94 days (last pass: next-20200214 - first fail: next-20200217)

    versatile_defconfig:
        gcc-8:
          versatile-pb:
              lab-collabora: failing since 3 days (last pass: next-20200515 - first fail: next-20200518)

arm64:

    defconfig:
        gcc-8:
          meson-g12a-u200:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-g12a-x96-max:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-g12b-a311d-khadas-vim3:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-g12b-odroid-n2:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-sm1-khadas-vim3l:
              lab-baylibre: new failure (last pass: next-20200515)
          meson-sm1-sei610:
              lab-baylibre: new failure (last pass: next-20200519)

    defconfig+CONFIG_CPU_BIG_ENDIAN=y:
        gcc-8:
          meson-sm1-khadas-vim3l:
              lab-baylibre: new failure (last pass: next-20200515)

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
          meson-g12a-u200:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-g12a-x96-max:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-g12b-a311d-khadas-vim3:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-g12b-odroid-n2:
              lab-baylibre: new failure (last pass: next-20200519)
          meson-sm1-khadas-vim3l:
              lab-baylibre: new failure (last pass: next-20200515)
          meson-sm1-sei610:
              lab-baylibre: new failure (last pass: next-20200519)

riscv:

    defconfig:
        gcc-8:
          sifive_fu540:
              lab-baylibre-seattle: failing since 56 days (last pass: next-20200326 - first fail: next-20200327)

Boot Failures Detected:

riscv:
    defconfig:
        gcc-8:
            sifive_fu540: 1 failed lab

arm:
    sama5_defconfig:
        gcc-8:
            at91-sama5d4_xplained: 1 failed lab

    multi_v7_defconfig:
        gcc-8:
            bcm2836-rpi-2-b: 1 failed lab

arm64:
    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
            meson-g12a-u200: 1 failed lab
            meson-g12a-x96-max: 1 failed lab
            meson-g12b-a311d-khadas-vim3: 1 failed lab
            meson-g12b-odroid-n2: 1 failed lab
            meson-sm1-khadas-vim3l: 1 failed lab
            meson-sm1-sei610: 1 failed lab
            mt7622-rfb1: 1 failed lab

    defconfig:
        gcc-8:
            meson-g12a-u200: 1 failed lab
            meson-g12a-x96-max: 1 failed lab
            meson-g12b-a311d-khadas-vim3: 1 failed lab
            meson-g12b-odroid-n2: 1 failed lab
            meson-sm1-khadas-vim3l: 1 failed lab
            meson-sm1-sei610: 1 failed lab
            mt7622-rfb1: 1 failed lab
            sm8150-mtp: 1 failed lab

    defconfig+CONFIG_CPU_BIG_ENDIAN=y:
        gcc-8:
            meson-sm1-khadas-vim3l: 1 failed lab

Offline Platforms:

arm:

    multi_v7_defconfig:
        gcc-8
            exynos5800-peach-pi: 1 offline lab
            qcom-apq8064-cm-qs600: 1 offline lab
            stih410-b2120: 1 offline lab

    exynos_defconfig:
        gcc-8
            exynos5800-peach-pi: 1 offline lab

---
For more info write to <info@kernelci.org>

                 reply index

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=5ec7fd1c.1c69fb81.c24e4.177f@mx.google.com \
    --to=bot@kernelci.org \
    --cc=linux-next@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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git