All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] ??? FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue)
Date: Tue, 3 Dec 2019 13:22:37 +0100	[thread overview]
Message-ID: <20191203122236.GC2844@rei> (raw)
In-Reply-To: <546bd6ac-8ab1-9a9b-5856-e6410fb8ee89@redhat.com>

Hi!
> > We ran automated tests on a recent commit from this kernel tree:
> > 
> >         Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
> >              Commit: cc9917b40848 - mdio_bus: Fix init if CONFIG_RESET_CONTROLLER=n
> > 
> > The results of these automated tests are provided below.
> > 
> >      Overall result: FAILED (see details below)
> >               Merge: OK
> >             Compile: OK
> >               Tests: FAILED
> > 
> > All kernel binaries, config files, and logs are available for download here:
> > 
> >    https://artifacts.cki-project.org/pipelines/309848
> > 
> > One or more kernel tests failed:
> > 
> >      ppc64le:
> >       ??? LTP
> 
> I see a slew of syscalls failures here for LTP:
> https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_resultoutputfile.log
> https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_syscalls.run.log

There are a few syslog failures, which does not seem to be related to
the kernel commit at all. The commit above seems to touch error handling
in a mdio bus which is used to configure network hardware. I would say
that this is connected to the rest of the unexplained failures on
ppc64le that seems to happen randomly.

-- 
Cyril Hrubis
chrubis@suse.cz

WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Rachel Sibley <rasibley@redhat.com>
Cc: CKI Project <cki-project@redhat.com>,
	Linux Stable maillist <stable@vger.kernel.org>,
	Memory Management <mm-qe@redhat.com>,
	LTP Mailing List <ltp@lists.linux.it>
Subject: Re: [LTP] ??? FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue)
Date: Tue, 3 Dec 2019 13:22:37 +0100	[thread overview]
Message-ID: <20191203122236.GC2844@rei> (raw)
In-Reply-To: <546bd6ac-8ab1-9a9b-5856-e6410fb8ee89@redhat.com>

Hi!
> > We ran automated tests on a recent commit from this kernel tree:
> > 
> >         Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
> >              Commit: cc9917b40848 - mdio_bus: Fix init if CONFIG_RESET_CONTROLLER=n
> > 
> > The results of these automated tests are provided below.
> > 
> >      Overall result: FAILED (see details below)
> >               Merge: OK
> >             Compile: OK
> >               Tests: FAILED
> > 
> > All kernel binaries, config files, and logs are available for download here:
> > 
> >    https://artifacts.cki-project.org/pipelines/309848
> > 
> > One or more kernel tests failed:
> > 
> >      ppc64le:
> >       ??? LTP
> 
> I see a slew of syscalls failures here for LTP:
> https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_resultoutputfile.log
> https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_syscalls.run.log

There are a few syslog failures, which does not seem to be related to
the kernel commit at all. The commit above seems to touch error handling
in a mdio bus which is used to configure network hardware. I would say
that this is connected to the rest of the unexplained failures on
ppc64le that seems to happen randomly.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2019-12-03 12:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 14:30 [LTP] ❌ FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue) CKI Project
2019-11-27 14:30 ` CKI Project
2019-11-27 15:06 ` [LTP] " Rachel Sibley
2019-11-27 15:06   ` Rachel Sibley
2019-12-03 12:22   ` Cyril Hrubis [this message]
2019-12-03 12:22     ` [LTP] ??? " Cyril Hrubis
2019-12-03 12:37     ` Jan Stancek
2019-12-03 12:37       ` Jan Stancek

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=20191203122236.GC2844@rei \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.