From: Jakub Racek <jracek@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Don Zickus <dzickus@redhat.com>, Sasha Levin <sashal@kernel.org>,
Memory Management <mm-qe@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>,
Jan Stancek <jstancek@redhat.com>,
CKI Project <cki-project@redhat.com>,
Zhaojuan Guo <zguo@redhat.com>
Subject: Re: ? FAIL: Stable queue: queue-5.3
Date: Wed, 16 Oct 2019 19:25:51 +0200 [thread overview]
Message-ID: <20191016172551.bijr2fqnrwylglu4@jra-laptop> (raw)
In-Reply-To: <CA+G9fYsKqnev+Ayu8-p8AY-4cxLJv-zTx4s-A9hxxB83R4Pejg@mail.gmail.com>
+++ 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 <dzickus@redhat.com> 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
next prev parent reply other threads:[~2019-10-16 17:26 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 22:11 ❌ FAIL: Stable queue: queue-5.3 CKI Project
2019-10-09 22:44 ` Sasha Levin
2019-10-10 1:09 ` Don Zickus
2019-10-10 6:30 ` Naresh Kamboju
2019-10-16 17:25 ` Jakub Racek [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-26 2:00 CKI Project
2019-11-22 1:23 CKI Project
2019-11-18 15:00 CKI Project
[not found] ` <8e0fa6de-b6b1-23ac-9e77-d425c8d1ba22@redhat.com>
2019-11-19 12:37 ` Laura Abbott
2019-11-19 12:44 ` Greg KH
2019-11-19 12:50 ` Laura Abbott
2019-11-21 17:53 ` Greg KH
2019-11-11 21:58 CKI Project
2019-11-11 19:57 CKI Project
2019-11-11 15:36 CKI Project
2019-11-11 20:10 ` Rachel Sibley
2019-11-11 20:47 ` Laura Abbott
2019-11-11 12:50 CKI Project
2019-11-11 11:43 CKI Project
2019-11-10 16:12 CKI Project
2019-11-08 23:24 CKI Project
2019-11-08 21:16 CKI Project
2019-11-08 21:55 ` Ondrej Mosnacek
2019-11-08 5:51 CKI Project
2019-11-06 20:56 CKI Project
2019-11-07 10:22 ` Hangbin Liu
2019-11-05 2:51 CKI Project
2019-11-05 1:14 CKI Project
2019-11-05 6:37 ` Greg KH
2019-11-05 8:15 ` Naresh Kamboju
2019-11-04 11:21 CKI Project
2019-10-30 20:12 CKI Project
2019-10-29 20:22 CKI Project
2019-10-29 17:48 CKI Project
2019-10-28 2:44 CKI Project
2019-10-28 2:30 CKI Project
2019-10-28 1:22 CKI Project
2019-10-27 23:47 CKI Project
2019-10-27 14:34 CKI Project
2019-10-27 9:18 CKI Project
2019-10-27 9:08 CKI Project
2019-10-27 9:20 ` Sasha Levin
2019-10-26 22:33 CKI Project
2019-10-27 7:02 ` Naresh Kamboju
2019-10-27 9:32 ` Jan Stancek
2019-10-25 11:25 CKI Project
2019-10-22 2:54 CKI Project
2019-10-16 14:03 CKI Project
2019-10-16 13:56 CKI Project
2019-10-15 22:30 CKI Project
2019-10-15 6:39 CKI Project
2019-10-15 4:49 CKI Project
2019-10-10 13:17 CKI Project
2019-10-10 10:26 CKI Project
2019-10-10 10:51 ` Veronika Kabatova
2019-10-10 6:43 CKI Project
2019-10-08 19:17 CKI Project
2019-10-08 19:10 CKI Project
2019-10-08 18:03 CKI Project
2019-10-08 18:57 ` Greg KH
2019-10-06 4:57 CKI Project
2019-10-01 19:25 CKI Project
2019-10-01 18:32 CKI Project
2019-10-01 19:19 ` Greg KH
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=20191016172551.bijr2fqnrwylglu4@jra-laptop \
--to=jracek@redhat.com \
--cc=cki-project@redhat.com \
--cc=dzickus@redhat.com \
--cc=jstancek@redhat.com \
--cc=mm-qe@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zguo@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;
as well as URLs for NNTP newsgroup(s).