mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Cc: kernel test robot <rong.a.chen@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [selftests] 7cb32086e5: kernel-selftests.x86.check_initial_reg_state_32.fail
Date: Fri, 10 Jul 2020 08:18:49 -0600	[thread overview]
Message-ID: <8316a170-4aee-eb57-9038-3afb91c6f0e2@linuxfoundation.org> (raw)
In-Reply-To: <CANoWswkjNnyBi68HL6VjX9dWt6VdjxycXV09j5L+jkCAbnrHrg@mail.gmail.com>

On 7/10/20 12:02 AM, Yauheni Kaliuta wrote:
> On Thu, Jul 9, 2020 at 6:36 PM Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> On 7/9/20 12:49 AM, kernel test robot wrote:
>>> Greeting,
>>>
>>> FYI, we noticed the following commit (built with gcc-9):
>>>
>>> commit: 7cb32086e59b514a832a3e11f5370d37e7cfe022 ("selftests: simplify run_tests")
>>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>>>
>>>
>>
>> Thanks for the report. I will drop this patch for now from next.
>>
>> Yauheni,
>>
>> This patch broke x86 32-bit test run
>> make run_tests -C x86
>>
>> Please resubmit the patch with the fix.
> 
> I did not check carefully the report, but isn't it expected that some
> tests are moved after the patch since they originally were placed
> incorrectly?
> 
> 
The failure doesn't have anything to do with test being moved. You can
reproduce this very easily by running make as shown below in x86 dir
under tools/testing/selftests

make run_tests -C x86

I reproduced the problem with your and patch and verified that the
problem tracks your patch. I dropped the patch from linux-next
Your other two patches in the series are fine.

In any case, this patch isn't really adding any functionality and
is a good cleanup. Let's do the cleanup right or not.

thanks,
-- Shuah

  reply	other threads:[~2020-07-10 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200709064946.GQ3874@shao2-debian>
2020-07-09 15:36 ` Shuah Khan
2020-07-10  6:02   ` Yauheni Kaliuta
2020-07-10 14:18     ` Shuah Khan [this message]
2020-07-13 11:27       ` Yauheni Kaliuta

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=8316a170-4aee-eb57-9038-3afb91c6f0e2@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=rong.a.chen@intel.com \
    --cc=yauheni.kaliuta@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

Powered by JetHome