From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: lersek@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by groups.io with SMTP; Thu, 08 Aug 2019 16:29:20 -0700 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3B2D53082B1F; Thu, 8 Aug 2019 23:29:20 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-28.ams2.redhat.com [10.36.116.28]) by smtp.corp.redhat.com (Postfix) with ESMTP id CE44B10016E8; Thu, 8 Aug 2019 23:29:18 +0000 (UTC) Subject: Re: [edk2-devel] [Patch 00/10 V8] Enable multiple process AutoGen From: "Laszlo Ersek" To: "Feng, Bob C" , "devel@edk2.groups.io" , "leif.lindholm@linaro.org" Cc: Andrew Fish , "Kinney, Michael D" , "Gao, Liming" References: <20190807042537.11928-1-bob.c.feng@intel.com> <20190808134522.GY25813@bivouac.eciton.net> <08650203BA1BD64D8AD9B6D5D74A85D160B559E9@SHSMSX105.ccr.corp.intel.com> Message-ID: Date: Fri, 9 Aug 2019 01:29:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.45]); Thu, 08 Aug 2019 23:29:20 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 08/09/19 00:18, Laszlo Ersek wrote: > On 08/08/19 17:38, Feng, Bob C wrote: >> Hi Laszlo and Leif, >> >> Thanks for you detailed testing and comments. >> >> I'd like to explain the failure of the test 3#. I can reproduce the failure with your steps and I found this failure can also be reproduced without multiple process autogen patch set. I debugged and found this failure is due to --hash build option. I double tested that if remove --hash build option, the test 3# can pass. Would you please double verified test 3# without --hash? >> >> I think we can enter a new BZ for the --hash bug. > > Confirmed -- with "--hash" removed from the build command line, the build is picked up fine after Ctrl-C. (And the firmware binary is sound.) > > So, my ACK stands. > > ( > > And now I remember that in my v3 testing, I also omitted "--hash": > > http://mid.mail-archive.com/4ea3d3fa-2210-3642-2337-db525312d312@redhat.com > https://edk2.groups.io/g/devel/message/44246 > > At the bottom I stated that I didn't test "--hash". > > ) ... based on the above, I can even provide: Tested-by: Laszlo Ersek for the series. Thanks Laszlo