public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: "Benoît Cousson" <bcousson@baylibre•com>,
	"Tony Lindgren" <tony@atomide•com>
Cc: linux-omap@vger•kernel.org, linux-next@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org
Subject: Re: next/master boot: 257 boots: 11 failed, 229 passed with 16 offline, 1 conflict (next-20190604)
Date: Tue, 4 Jun 2019 17:00:18 +0100	[thread overview]
Message-ID: <20190604160018.GI2456@sirena.org.uk> (raw)
In-Reply-To: <5cf685d0.1c69fb81.e3d89.43ae@mx.google.com>


[-- Attachment #1.1: Type: text/plain, Size: 517 bytes --]

On Tue, Jun 04, 2019 at 07:53:04AM -0700, kernelci.org bot wrote:

Today's -next fails to boot omap2plus_defconfig on Beagle XM:

>     omap2plus_defconfig:
>         gcc-8:
>           omap3-beagle-xm:
>               lab-baylibre: failing since 1 day (last pass: next-20190531 - first fail: next-20190603)

The boot fails silently with no output after the bootloader:

    https://kernelci.org/boot/id/5cf655fc59b5149acad51504/

which isn't much to go on, it does seem to have been OK in
multi_v7_defconfig though.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

       reply	other threads:[~2019-06-04 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5cf685d0.1c69fb81.e3d89.43ae@mx.google.com>
2019-06-04 16:00 ` Mark Brown [this message]
2019-06-10  6:41   ` next/master boot: 257 boots: 11 failed, 229 passed with 16 offline, 1 conflict (next-20190604) Tony Lindgren
2019-06-04 16:23 ` Mark Brown

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=20190604160018.GI2456@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=bcousson@baylibre$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-omap@vger$(echo .)kernel.org \
    --cc=tony@atomide$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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