Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Niklas Cassel <niklas.cassel@linaro.org>
Cc: kernel-build-reports@lists.linaro.org,
	linux-arm-msm@vger.kernel.org,
	David Brown <david.brown@linaro.org>,
	linux-next@vger.kernel.org, Andy Gross <andy.gross@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot: 179 boots: 11 failed, 167 passed with 1 offline (next-20180731)
Date: Wed, 1 Aug 2018 10:31:02 +0100	[thread overview]
Message-ID: <20180801093102.GB5509@sirena.org.uk> (raw)
In-Reply-To: <20180731195037.GA6737@centauri.lan>


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

On Tue, Jul 31, 2018 at 09:50:37PM +0200, Niklas Cassel wrote:

> I guess it could be a bug that does not trigger on every boot,
> or it could be a problem in the kernelci infrastructure.

Infrastructure bugs *tend* to manifest differently to this FWIW, though
it can never be excluded.

[-- 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:[~2018-08-01  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5b607cc4.1c69fb81.6c1d6.6534@mx.google.com>
2018-07-31 16:06 ` next/master boot: 179 boots: 11 failed, 167 passed with 1 offline (next-20180731) Mark Brown
2018-08-01  8:19   ` Ludovic BARRE
2018-08-01  9:58     ` Ulf Hansson
2018-08-01 10:05   ` Ulf Hansson
2018-07-31 16:11 ` Mark Brown
2018-07-31 19:50   ` Niklas Cassel
2018-08-01  9:31     ` Mark Brown [this message]
2018-08-01 20:50       ` Bjorn Andersson

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=20180801093102.GB5509@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=andy.gross@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=niklas.cassel@linaro.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