All of lore.kernel.org
 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 boot: 53 boots: 3 failed, 49 passed with 1 untried/unknown (gpio-v5.5-3-31-g4e4ade156406)
Date: Mon, 13 Jan 2020 18:45:29 -0800 (PST)	[thread overview]
Message-ID: <5e1d2b49.1c69fb81.d3464.436e@mx.google.com> (raw)

linusw/for-next boot: 53 boots: 3 failed, 49 passed with 1 untried/unknown (gpio-v5.5-3-31-g4e4ade156406)

Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/for-next/kernel/gpio-v5.5-3-31-g4e4ade156406/
Full Build Summary: https://kernelci.org/build/linusw/branch/for-next/kernel/gpio-v5.5-3-31-g4e4ade156406/

Tree: linusw
Branch: for-next
Git Describe: gpio-v5.5-3-31-g4e4ade156406
Git Commit: 4e4ade15640646ddff45d1235d6c08086b98c645
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 46 unique boards, 14 SoC families, 3 builds out of 5

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        gcc-8:
          rk3288-rock2-square:
              lab-collabora: failing since 13 days (last pass: v5.5-rc1-20-g06c4fc5eda6b - first fail: v5.5-rc4-9-g331d7ae3fa15)
          sun4i-a10-olinuxino-lime:
              lab-baylibre: new failure (last pass: v5.5-rc4-35-g0dc4997ef739)

arm64:

    defconfig:
        gcc-8:
          meson-gxl-s805x-p241:
              lab-baylibre: new failure (last pass: v5.5-rc4-35-g0dc4997ef739)
          meson-gxl-s905x-khadas-vim:
              lab-baylibre: new failure (last pass: v5.5-rc4-35-g0dc4997ef739)

Boot Failures Detected:

arm64:
    defconfig:
        gcc-8:
            meson-gxl-s805x-p241: 1 failed lab
            meson-gxl-s905x-khadas-vim: 1 failed lab

arm:
    multi_v7_defconfig:
        gcc-8:
            rk3288-rock2-square: 1 failed lab

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

                 reply	other threads:[~2020-01-14  2:45 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=5e1d2b49.1c69fb81.d3464.436e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.