From: Greg KH <greg@kroah.com>
To: Justin Forbes <jmforbes@linuxtx.org>
Cc: Veronika Kabatova <vkabatov@redhat.com>,
CKI Project <cki-project@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ❌ FAIL: Test report for kernel 5.13.2 (stable-queue, ee00910f)
Date: Fri, 16 Jul 2021 20:05:03 +0200 [thread overview]
Message-ID: <YPHKT9BFB18PjO8h@kroah.com> (raw)
In-Reply-To: <CAFxkdArnhDFD4rH4__DU0tKxxBd_3s4vGRVeXpZuunxU1u=m6Q@mail.gmail.com>
On Thu, Jul 15, 2021 at 03:30:32PM -0500, Justin Forbes wrote:
> On Thu, Jul 15, 2021 at 12:31 PM Greg KH <greg@kroah.com> wrote:
> >
> > On Thu, Jul 15, 2021 at 02:51:15PM +0200, Veronika Kabatova wrote:
> > > On Thu, Jul 15, 2021 at 2:50 PM CKI Project <cki-project@redhat.com> wrote:
> > > >
> > > >
> > > > Hello,
> > > >
> > > > We ran automated tests on a recent commit from this kernel tree:
> > > >
> > > > Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > > Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window close
> > > >
> > > > The results of these automated tests are provided below.
> > > >
> > > > Overall result: FAILED (see details below)
> > > > Merge: OK
> > > > Compile: FAILED
> > > >
> > > > All kernel binaries, config files, and logs are available for download here:
> > > >
> > > > https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/07/15/337656806
> > > >
> > > > We attempted to compile the kernel for multiple architectures, but the compile
> > > > failed on one or more architectures:
> > > >
> > > > ppc64le: FAILED (see build-ppc64le.log.xz attachment)
> > > > x86_64: FAILED (see build-x86_64.log.xz attachment)
> > > >
> > >
> > > Hi, looks to be introduced by
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=queue/5.13&id=07d407cc1259634b3334dd47519ecd64e6818617
> >
> > Are you sure? I fixed a different build bug in that area a few hours
> > ago, if you rebuild the tree it should be resolved.
> >
> > If not, please let me know.
> >
>
> Seeing the same issue here, there is nothing new in the tree.
Ok, see it now, dropped the offending patch.
thanks,
greg k-h
prev parent reply other threads:[~2021-07-16 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 12:49 ❌ FAIL: Test report for kernel 5.13.2 (stable-queue, ee00910f) CKI Project
2021-07-15 12:51 ` Veronika Kabatova
2021-07-15 17:31 ` Greg KH
2021-07-15 19:36 ` Veronika Kabatova
2021-07-15 19:54 ` Justin Forbes
2021-07-16 18:05 ` Greg KH
2021-07-15 20:30 ` Justin Forbes
2021-07-16 18:05 ` Greg KH [this message]
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=YPHKT9BFB18PjO8h@kroah.com \
--to=greg@kroah.com \
--cc=cki-project@redhat.com \
--cc=jmforbes@linuxtx.org \
--cc=stable@vger.kernel.org \
--cc=vkabatov@redhat.com \
/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