linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 14
Date: Mon, 14 Mar 2016 16:51:51 +0000	[thread overview]
Message-ID: <56E6EC27.2090700@arm.com> (raw)
In-Reply-To: <20160314143729.GA31845@roeck-us.net>

Hi Guenter,

On 14/03/16 14:37, Guenter Roeck wrote:
> To give people an idea what to expect in the merge window, here are my current
> build and runtime test results. Some of the runtime failures are due to the
> newly introduced i2c bug, but many (including the arm64 boot failures) have
> been around for a while.

> Qemu test results:
> 	total: 96 pass: 69 fail: 27
> Failed tests:

> 	arm64:smp:defconfig

This may be due to this qemu bug: http://patchwork.ozlabs.org/patch/585237/


> 	arm64:nosmp:defconfig

Since 4b3dc9679cf7 ("arm64: force CONFIG_SMP=y and remove redundant #ifdefs"),
this may just be testing the smp case again - unless your qemu config is
different too.


> Details are available at http://kerneltests.org/builders.

Thanks - this looks like a mine of information!


James

  reply	other threads:[~2016-03-14 16:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  6:40 linux-next: Tree for Mar 14 Stephen Rothwell
2016-03-14 14:37 ` Guenter Roeck
2016-03-14 16:51   ` James Morse [this message]
2016-03-14 19:18     ` Guenter Roeck
2016-03-14 23:55   ` Michael Ellerman
2016-03-15  2:31     ` Guenter Roeck
2016-03-15  5:26   ` linux-next: Tree for Mar 14 (mips qemu failure bisected) Guenter Roeck
2016-03-15 21:55     ` Qais Yousef
2016-03-16  0:17       ` Guenter Roeck
2016-03-16 13:22         ` Guenter Roeck
2016-03-16 20:27           ` Qais Yousef
2016-03-16 22:17             ` Qais Yousef
2016-03-17  2:10               ` Guenter Roeck
2016-03-17  2:36               ` Guenter Roeck
     [not found]                 ` <CA+mqd+5AUfGSh1WvLa5bOt-HQM=eA+BmLeb7_xZo+-tswLcqiQ@mail.gmail.com>
2016-03-17 12:43                   ` Guenter Roeck
2016-03-15  0:30 ` linux-next: Tree for Mar 14 Sergey Senozhatsky
2016-03-15  6:43   ` Wolfram Sang
2016-03-15  6:52     ` Sergey Senozhatsky
  -- strict thread matches above, loose matches on Subject: below --
2024-03-14  3:22 Stephen Rothwell
2023-03-14  3:24 Stephen Rothwell
2018-03-14  6:27 Stephen Rothwell
2014-03-14 19:32 Mark Brown
2013-03-14  7:06 Stephen Rothwell
2012-03-14  7:19 Stephen Rothwell

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=56E6EC27.2090700@arm.com \
    --to=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sfr@canb.auug.org.au \
    /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).