All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: lkp@lists.01.org
Subject: Re: More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed
Date: Tue, 26 Jul 2016 17:18:59 -0400	[thread overview]
Message-ID: <20160726211859.GB9577@codemonkey.org.uk> (raw)
In-Reply-To: <87wpk8p49p.fsf@x220.int.ebiederm.org>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Tue, Jul 26, 2016 at 02:50:58PM -0500, Eric W. Biederman wrote:

 > > Yes that's the right directions to follow. We'll make the reports more
 > > understandable and the test/bisects more reliable.
 > 
 > Thanks.  Does trinity have a random seed it can export/import to rerun
 > the same tests?  I ask because there was a failure these tests caught
 > that if the right kernel options was enabled was 100% reliable and it
 > blamed a commit 10 patches down from the indicated commit.

It does log the random seed on startup, and can replay it with the -s option

There is some variance if you were to do two runs with the same seed back
to back, because on startup, it walks /proc & /sys, and they'd see different things
so for eg "read() from fd 100" might mean something entirely different.

But as the testbot runs a pretty minimal userspace, only runs trinity once,
and really early in boot, this point might not matter.

	Dave

WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@codemonkey.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	containers@lists.linux-foundation.org, lkp@01.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed
Date: Tue, 26 Jul 2016 17:18:59 -0400	[thread overview]
Message-ID: <20160726211859.GB9577@codemonkey.org.uk> (raw)
In-Reply-To: <87wpk8p49p.fsf@x220.int.ebiederm.org>

On Tue, Jul 26, 2016 at 02:50:58PM -0500, Eric W. Biederman wrote:

 > > Yes that's the right directions to follow. We'll make the reports more
 > > understandable and the test/bisects more reliable.
 > 
 > Thanks.  Does trinity have a random seed it can export/import to rerun
 > the same tests?  I ask because there was a failure these tests caught
 > that if the right kernel options was enabled was 100% reliable and it
 > blamed a commit 10 patches down from the indicated commit.

It does log the random seed on startup, and can replay it with the -s option

There is some variance if you were to do two runs with the same seed back
to back, because on startup, it walks /proc & /sys, and they'd see different things
so for eg "read() from fd 100" might mean something entirely different.

But as the testbot runs a pretty minimal userspace, only runs trinity once,
and really early in boot, this point might not matter.

	Dave

  reply	other threads:[~2016-07-26 21:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 21:20 [fs] 54cc07a761: BUG: kernel test crashed kernel test robot
2016-07-23 21:20 ` kernel test robot
     [not found] ` <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-07-23 21:52   ` Eric W. Biederman
2016-07-23 21:52     ` Eric W. Biederman
2016-07-23 21:52     ` Eric W. Biederman
2016-07-25 18:57   ` More information please. " Eric W. Biederman
2016-07-25 18:57     ` Eric W. Biederman
2016-07-25 18:57     ` Eric W. Biederman
     [not found]     ` <877fc9a6mb.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 14:35       ` [LKP] " Fengguang Wu
2016-07-26 14:35         ` Fengguang Wu
2016-07-26 14:35         ` Fengguang Wu
     [not found]         ` <20160726143545.GA23656-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-26 14:52           ` [LKP] " Eric W. Biederman
2016-07-26 14:52             ` Eric W. Biederman
2016-07-26 14:52             ` Eric W. Biederman
     [not found]             ` <87vazsv4cn.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 15:13               ` [LKP] " Fengguang Wu
2016-07-26 15:13                 ` Fengguang Wu
2016-07-26 15:13                 ` Fengguang Wu
     [not found]                 ` <20160726151344.GB8811-q6ZYBFIlbFFi0tQiZxhdj1DQ4js95KgL@public.gmane.org>
2016-07-26 19:50                   ` [LKP] " Eric W. Biederman
2016-07-26 19:50                     ` Eric W. Biederman
2016-07-26 19:50                     ` Eric W. Biederman
2016-07-26 21:18                     ` Dave Jones [this message]
2016-07-26 21:18                       ` [LKP] " Dave Jones
     [not found]                     ` <87wpk8p49p.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-07-26 21:18                       ` Dave Jones
2016-07-26 21:15                   ` Dave Jones
2016-07-26 21:15                 ` Dave Jones
2016-07-26 21:15                   ` [LKP] " Dave Jones

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=20160726211859.GB9577@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=lkp@lists.01.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.