From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 57142C0650E for ; Wed, 3 Jul 2019 12:32:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 32E26218A0 for ; Wed, 3 Jul 2019 12:32:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726217AbfGCMcB convert rfc822-to-8bit (ORCPT ); Wed, 3 Jul 2019 08:32:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55590 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726255AbfGCMcB (ORCPT ); Wed, 3 Jul 2019 08:32:01 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 238E18553A; Wed, 3 Jul 2019 12:32:01 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 16E098D56; Wed, 3 Jul 2019 12:32:01 +0000 (UTC) Received: from zmail19.collab.prod.int.phx2.redhat.com (zmail19.collab.prod.int.phx2.redhat.com [10.5.83.22]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 066E6E160; Wed, 3 Jul 2019 12:32:01 +0000 (UTC) Date: Wed, 3 Jul 2019 08:32:00 -0400 (EDT) From: Veronika Kabatova To: Greg KH Cc: CKI Project , Linux Stable maillist Message-ID: <1065329137.28552653.1562157120223.JavaMail.zimbra@redhat.com> In-Reply-To: <20190703120759.GA7784@kroah.com> References: <20190703112520.GA20712@kroah.com> <1989107726.28546762.1562155276612.JavaMail.zimbra@redhat.com> <20190703120759.GA7784@kroah.com> Subject: =?utf-8?Q?Re:_=E2=9D=8C_FAIL:_Stable_queue:_queue-5.1?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Originating-IP: [10.40.205.46, 10.4.195.17] Thread-Topic: =?utf-8?B?4p2MIEZBSUw6?= Stable queue: queue-5.1 Thread-Index: 9f+C+3fXqxnSUEWLYwNLl+NHhWG8qA== X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 03 Jul 2019 12:32:01 +0000 (UTC) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org ----- Original Message ----- > From: "Greg KH" > To: "Veronika Kabatova" > Cc: "CKI Project" , "Linux Stable maillist" > Sent: Wednesday, July 3, 2019 2:07:59 PM > Subject: Re: ❌ FAIL: Stable queue: queue-5.1 > > On Wed, Jul 03, 2019 at 08:01:16AM -0400, Veronika Kabatova wrote: > > > > > > ----- Original Message ----- > > > From: "Greg KH" > > > To: "CKI Project" > > > Cc: "Linux Stable maillist" > > > Sent: Wednesday, July 3, 2019 1:25:20 PM > > > Subject: Re: ❌ FAIL: Stable queue: queue-5.1 > > > > > > On Wed, Jul 03, 2019 at 07:16:58AM -0400, CKI Project wrote: > > > > Hello, > > > > > > > > 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: 8584aaf1c326 - Linux 5.1.16 > > > > > > > > The results of these automated tests are provided below. > > > > > > > > Overall result: FAILED (see details below) > > > > Merge: FAILED > > > > > > Guys, this is getting annoying, this is your test systems, the queue is > > > empty :) > > > > > > > Hi, > > > > this is not an empty queue problem (that should be fixed now). We triggered > > the testing right after the 5.1.16 was released to test the present queue > > with it. We have added the commit hash of the queue to the merge details in > > the report to verify this is indeed the case. > > > > The base commit for the stable kernel is 8584aaf1c326 > > The commit of the stable queue is d0f506ba82 > > > > This queue was removed a minute later (obviously with the release) after > > the > > baseline change was pushed but we caught this combo as we try to trigger > > testing after every change to any of those repos. So the patches from the > > queue really didn't apply. > > > > > > I currently see two ways (or their combination) around this: > > 1) The queue changes need to be pushed first > > Given that you are working behind a mirror of the "real" git trees, they > can, and probably will, get out of order, so there's no guarantee of > "first" here. > > And I am doing this in a scripted way, so they should be pushed within 1 > minute of each other at this point in time. > > > 2) We detect how long ago the baseline was pushed and if it's less than > > let's say 5mins we abort the pipeline to give you enough time to do the > > changes to the repo > > I say this is the best thing to do to help with the mirroring issues > involved. > Given the additional info you just mentioned I agree that this is the most reasonable solution. I'll work on implementing this as soon as I find some free time. Thanks again! Veronika > thanks, > > greg k-h >