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=-7.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 19B74FA3728 for ; Wed, 16 Oct 2019 17:26:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E3E0E2064B for ; Wed, 16 Oct 2019 17:26:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727793AbfJPRZ7 (ORCPT ); Wed, 16 Oct 2019 13:25:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48810 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726940AbfJPRZ7 (ORCPT ); Wed, 16 Oct 2019 13:25:59 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9644A20F2; Wed, 16 Oct 2019 17:25:58 +0000 (UTC) Received: from jra-laptop (unknown [10.43.17.34]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1E0B95D6A9; Wed, 16 Oct 2019 17:25:51 +0000 (UTC) Date: Wed, 16 Oct 2019 19:25:51 +0200 From: Jakub Racek To: Naresh Kamboju Cc: Don Zickus , Sasha Levin , Memory Management , Linux Stable maillist , Jan Stancek , CKI Project , Zhaojuan Guo Subject: Re: ? FAIL: Stable queue: queue-5.3 Message-ID: <20191016172551.bijr2fqnrwylglu4@jra-laptop> References: <20191009224437.GY1396@sasha-vm> <20191010010952.suo6opzifh5y37gm@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-OS: Linux jra-laptop 3.10.0-1062.el7.x86_64 x86_64 User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.redhat.com [10.5.110.71]); Wed, 16 Oct 2019 17:25:58 +0000 (UTC) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org +++ Naresh Kamboju [10/10/19 12:00 +0530]: >3831659 Warn Aborted cki@gitlab:214657 5.3.5-dc073f1.cki@upstream-stable aarch64 >3831713 Fail Completed cki@gitlab:214657 5.3.5-dc073f1.cki@upstream-stable aarch64 [RS:6067440] >3831660 Pass Completed cki@gitlab:214657 5.3.5-dc073f1.cki@upstream-stable ppc64le >3831662 Fail Completed cki@gitlab:214657 5.3.5-dc073f1.cki@upstream-stable x86_64 >3831661 Pass Completed cki@gitlab:214657 5.3.5-dc073f1.cki@upstream-stable x86_64 > >On Thu, 10 Oct 2019 at 06:40, Don Zickus wrote: >> >> On Wed, Oct 09, 2019 at 06:44:37PM -0400, Sasha Levin wrote: >> > On Wed, Oct 09, 2019 at 06:11:40PM -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: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git >> > > Commit: 52020d3f6633 - Linux 5.3.5 >> > > >> > > 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/214657 >> > > >> > > One or more kernel tests failed: >> > > >> > > x86_64: >> > > ✗ Boot test >> > > ✗ Boot test >> > > ✗ Boot test >> > > ✗ Boot test >> > >> > Hm, I looked here: >> > >> > https://artifacts.cki-project.org/pipelines/214657/logs/x86_64_host_1_Boot_test_dmesg.log >> > >> > and here: >> > >> > https://artifacts.cki-project.org/pipelines/214657/logs/x86_64_host_2_Boot_test_dmesg.log >> > >> > but both look sane. What am I missing? >> >> I don't believe you are. I looked at the raw beaker jobs and the x86_64 >> machines passed and another set is still queued. There is an aarch64 >> machine that failed to boot. >> >> Unfortunately, I am skeptical of this result too but I would wait for the >> CKI team to triage this. > >On the quick look i see > >x86_64: Host 3 failed to do any testing. >Is it an infrastructure problem ? > Sorry, this was a super weird bug in our CI. It has since been fixed. >- Naresh > -- Best regards, Jakub Racek ARK