mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "Liu, Yujie" <yujie.liu@intel.com>,
	"masahiroy@kernel.org" <masahiroy@kernel.org>
Cc: "Li, Philip" <philip.li@intel.com>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
	lkp <lkp@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [kbuild test robot] random-order parallel building
Date: Fri, 9 Jun 2023 08:14:49 -0700	[thread overview]
Message-ID: <92c0209a-ba4e-0b8a-a4dd-6077a75d3378@infradead.org> (raw)
In-Reply-To: <7403dd164cff7d9217999cddb66135db47564c4b.camel@intel.com>



On 6/9/23 01:41, Liu, Yujie wrote:
> Hi Masahiro,
> 
> On Fri, 2023-05-12 at 15:09 +0800, Philip Li wrote:
>> On Fri, May 12, 2023 at 12:25:13PM +0900, Masahiro Yamada wrote:
>>> Hello, maintainers of the kbuild test robot.
>>>
>>> I have a proposal for the 0day tests.
>> Thanks a lot for the proposal for the shuffle make, we will do some
>> investigation to try this random order parallel build. The gnu make
>> we currently use is 4.3, we will try the 4.4 to see any problem.
>>
>> For the timeline, we may provide update later this month.
> We've upgraded to make v4.4.1 in kernel test robot and enabled random-
> order parallel compiling in our randconfig build tests. The shuffle
> seed is generated by hashing the randconfig, so it changes overtime and
> can cover various random orders. We are still doing some internal
> testing and will put it online once everything is done.
> 

I have also been using it since this proposal was submitted.
I haven't seen any issues with it.

thanks.
-- 
~Randy

  reply	other threads:[~2023-06-09 15:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  3:25 Masahiro Yamada
2023-05-12  7:09 ` Philip Li
2023-06-09  8:41   ` Liu, Yujie
2023-06-09 15:14     ` Randy Dunlap [this message]
2023-06-09 15:59     ` Masahiro Yamada

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=92c0209a-ba4e-0b8a-a4dd-6077a75d3378@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=masahiroy@kernel.org \
    --cc=philip.li@intel.com \
    --cc=yujie.liu@intel.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

all inboxes | Powered by JetHome®