All of lore.kernel.org
 help / color / mirror / Atom feed
From: Veronika Kabatova <vkabatov@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: catalin marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	CKI Project <cki-project@redhat.com>
Subject: Re: ❌ FAIL: Test	report?for?kernel?5.11.0-rc7 (arm-next)
Date: Wed, 10 Feb 2021 14:31:45 -0500 (EST)	[thread overview]
Message-ID: <719557748.27305363.1612985505202.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20210210185602.GA29192@willie-the-truck>



----- Original Message -----
> From: "Will Deacon" <will@kernel.org>
> To: "Veronika Kabatova" <vkabatov@redhat.com>
> Cc: "catalin marinas" <catalin.marinas@arm.com>, "CKI Project" <cki-project@redhat.com>,
> linux-arm-kernel@lists.infradead.org
> Sent: Wednesday, February 10, 2021 7:56:03 PM
> Subject: Re: ❌ FAIL: Test	report?for?kernel?5.11.0-rc7 (arm-next)
> 
> On Wed, Feb 10, 2021 at 01:06:08PM -0500, Veronika Kabatova wrote:
> > 
> > 
> > ----- Original Message -----
> > > From: "Will Deacon" <will@kernel.org>
> > > To: "Veronika Kabatova" <vkabatov@redhat.com>
> > > Cc: "catalin marinas" <catalin.marinas@arm.com>, "CKI Project"
> > > <cki-project@redhat.com>,
> > > linux-arm-kernel@lists.infradead.org
> > > Sent: Wednesday, February 10, 2021 6:31:34 PM
> > > Subject: Re: ❌ FAIL: Test report	for?kernel?5.11.0-rc7 (arm-next)
> > > 
> > > On Wed, Feb 10, 2021 at 12:07:23PM -0500, Veronika Kabatova wrote:
> > > > > On Wed, Feb 10, 2021 at 10:24:31AM -0500, Veronika Kabatova wrote:
> > > > > > Hi, I have a few results back:
> > > > > > 
> > > > > > - resubmitted the same kernel: gets stuck in the same spot
> > > > > > - tried the new version pushed today: gets stuck in the same spot
> > > > > 
> > > > > That's odd, as I just received a pass report for that branch!
> > > > > 
> > > > > https://lore.kernel.org/r/cki.598435E2D5.M3C5MKJ1NV@redhat.com
> > > > > 
> > > > > Is it just flakey, perhaps? Obviously, that's not great either, but
> > > > > it
> > > > > will
> > > > > make bisection more challenging.
> > > > > 
> > > > 
> > > > We have a large number of machines (both physical and virtual) and it's
> > > > impossible to run all tests on all of them, so they are randomly picked
> > > > as
> > > > long as they fit the distro and test requirements. The distribution for
> > > > ARM tree is 1 physical and 1 "any" machine (which usually ends up being
> > > > virtual). The jobs from the report you linked ran on different machines
> > > > and didn't pick the one that failed to boot previously, so I manually
> > > > forced my testing to pick that machine to eliminate some variables.
> > > 
> > > Ah thanks, I hadn't twigged that it was a different set of hosts each
> > > time.
> > > Makes sense.
> > > 
> > > > The machine in question can on course be somewhat flaky (hard to
> > > > eliminate
> > > > that possibility completely), but I checked our historical data and it
> > > > didn't fail to boot a single time other than with these two new
> > > > kernels.
> > > 
> > > So the first thing we should probably try is whether vanilla -rc7 fails
> > > on
> > > the machine causing us problems. If it does, then the arm64 queue for
> > > 5.12
> > > is out of the equation, if not then we can try a targetted bisection.
> > > 
> > > Would you be able to try v5.11-rc7 please?
> > 
> > Can do.
> 
> Brill, thanks.
> 
> > Someone snatched up the machine in the meanwhile and appears to have it
> > reserved till next Monday :/ I sincerely hope that they'll release it
> > sooner
> > and have queued up the test job with high priority. Will let you know right
> > as I get the results.
> 
> Just tell them the machine is broken and they really don't want to use it
> for anything important ;)
> 

Our wishes were granted by the lab fairy and the machine was returned
rather quickly :)

The 5.11-rc7 kernel boots.


Veronika

> Will
> 
> 
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-02-10 19:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 21:07 ❌ FAIL: Test report for kernel 5.11.0-rc7 (arm-next) CKI Project
2021-02-10  9:29 ` Will Deacon
2021-02-10 12:01   ` Veronika Kabatova
2021-02-10 15:24     ` Veronika Kabatova
2021-02-10 16:09       ` ❌ FAIL: Test report for kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 17:07         ` Veronika Kabatova
2021-02-10 17:31           ` ❌ FAIL: Test report for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 18:06             ` Veronika Kabatova
2021-02-10 18:56               ` ❌ FAIL: Test report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 19:31                 ` Veronika Kabatova [this message]
2021-02-10 20:17                   ` ❌ FAIL: Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-10 20:32                     ` Will Deacon
2021-02-11 10:46                       ` Veronika Kabatova
2021-02-11 11:50                         ` ❌ FAIL:?Test?report?for?kernel?5.11.0-rc7 (arm-next) Will Deacon
2021-02-11 12:25                           ` Veronika Kabatova
2021-02-15 13:13                             ` Veronika Kabatova
2021-02-15 18:24                               ` Will Deacon

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=719557748.27305363.1612985505202.JavaMail.zimbra@redhat.com \
    --to=vkabatov@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.