lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <513584ee-5247-fae1-4e5b-02f270d139f9@intel.com>
Date:   Fri, 25 Mar 2022 21:07:35 +0800
From:   "Chen, Rong A" <rong.a.chen@...el.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Nathan Chancellor <nathan@...nel.org>,
        kernel test robot <lkp@...el.com>, x86-ml <x86@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [tip:sched/core] BUILD SUCCESS
 3387ce4d8a5f2956fab827edf499fe6780e83faa



On 3/25/2022 7:54 PM, Peter Zijlstra wrote:
> On Fri, Mar 25, 2022 at 06:45:24PM +0800, Chen, Rong A wrote:
> 
>>> Oh *PLEASE* never report a branch as building if there's errors.
>>> It could be I (force) push a branch multiple times before I get any
>>> 0day reports back (0day has gotten *soooo* slow) so I only ever look at
>>> the latest report -- possibly days later.
>>
>> Hi Peter,
>>
>> Sorry for the bad experience, I'm not sure the meaning of "a branch as
>> building", is there a way to know the branch is not ready, or we can
>> postpone the test for a branch by a day?
> 
> I was just commenting in general; never send a mail with "SUCCESS" in
> the subject (as per this thread) when there are errors/warns with it,
> supressed or otherwise.
> 
> If you do want to supress warnings (I'm not sure why; a few more emails
> in my inbox really aren't going to make a difference) then please state
> so explicitly with a link to the email with the report.
> 
> The thing I worry about is that I often wait for a SUCCESS mail from
> 0day robot before I push code to tip. If the SUCCESS is unreliable, this
> is not good.
> 

Hi Peter,

Thanks for your advice, we will fix the problem in the near future.

Best Regards,
Rong Chen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ