From: Greg KH <greg@kroah.com>
To: Major Hayden <major@redhat.com>
Cc: CKI Project <cki-project@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ❎ FAIL: Stable queue: queue-5.1
Date: Thu, 9 May 2019 15:14:54 +0200 [thread overview]
Message-ID: <20190509131454.GA19094@kroah.com> (raw)
In-Reply-To: <8eb2f12e-818e-caf9-ac64-6652ec6beaf6@redhat.com>
On Thu, May 09, 2019 at 07:49:52AM -0500, Major Hayden wrote:
> On 5/9/19 7:47 AM, CKI Project wrote:
> > We ran automated tests on a patchset that was proposed for merging into this
> > kernel tree. The patches were applied to:
> >
> > Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> > Commit: e93c9c99a629 - Linux 5.1
> >
> > The results of these automated tests are provided below.
> >
> > Overall result: FAILED (see details below)
> > Merge: FAILED
> >
> > When we attempted to merge the patchset, we received an error:
> >
> > Patch is empty.
> >
> > We hope that these logs can help you find the problem quickly. For the full
> > detail on our testing procedures, please scroll to the bottom of this message.
> >
> > Please reply to this email if you have any questions about the tests that we
> > ran or if you have any suggestions on how to make future tests more effective.
> >
> > ,-. ,-.
> > ( C ) ( K ) Continuous
> > `-',-.`-' Kernel
> > ( I ) Integration
> > `-'
> > ______________________________________________________________________________
> >
> > Merge testing
> > -------------
> >
> > We cloned this repository and checked out the following commit:
> >
> > Repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> > Commit: e93c9c99a629 - Linux 5.1
> >
> > We then merged the patchset with `git am`:
>
> It looks like one of the patches moved away between the time our test began and when we tried to merge the patches. :)
Moved on the kernel.org side? I haven't removed any 5.1 patches from
the queue.
next prev parent reply other threads:[~2019-05-09 13:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 12:47 ❎ FAIL: Stable queue: queue-5.1 CKI Project
2019-05-09 12:49 ` Major Hayden
2019-05-09 13:14 ` Greg KH [this message]
2019-05-09 13:24 ` Major Hayden
-- strict thread matches above, loose matches on Subject: below --
2019-05-14 17:18 CKI Project
2019-05-14 17:26 ` Greg KH
2019-05-14 17:39 ` Major Hayden
2019-05-17 14:56 CKI Project
2019-05-17 15:01 ` Major Hayden
2019-06-15 9:57 CKI Project
2019-06-15 16:38 CKI Project
2019-06-15 16:54 ` Greg KH
2019-06-15 19:02 CKI Project
2019-06-15 19:12 CKI Project
2019-06-16 3:58 CKI Project
2019-06-16 14:22 CKI Project
2019-06-16 17:28 CKI Project
2019-06-20 0:13 CKI Project
2019-06-20 5:34 ` Greg KH
2019-06-23 16:11 CKI Project
2019-07-03 11:16 ❌ " CKI Project
2019-07-03 11:25 ` Greg KH
2019-07-03 12:01 ` Veronika Kabatova
2019-07-03 12:07 ` Greg KH
2019-07-03 12:32 ` Veronika Kabatova
2019-07-05 14:12 CKI Project
2019-07-05 14:57 ` Sasha Levin
2019-07-08 18:05 CKI Project
2019-07-08 18:23 ` Rachel Sibley
2019-07-09 4:41 ` ? " Murphy Zhou
2019-07-08 19:00 ❌ " CKI Project
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=20190509131454.GA19094@kroah.com \
--to=greg@kroah.com \
--cc=cki-project@redhat.com \
--cc=major@redhat.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).