From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mx.groups.io with SMTP id smtpd.web09.1666.1610099037616849177 for ; Fri, 08 Jan 2021 01:43:57 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=NyWsZAeD; spf=pass (domain: redhat.com, ip: 63.128.21.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610099036; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Z0pu37QZn9/WOHReDBzK6N/RVbjjbZ0YmQIzENyD09U=; b=NyWsZAeDQtDdQNVT6ktjR/ftL9LW9H+oqgJRlff58+ef8o8TAWf8djpQ1bNOBZIawUlHvg U74b4e0xXly5j2/Ws6QT44+3fJ4QBIOmFjgcrI+TsoVL2EASfspDa47TGggjy7oCHZCJPC lJSWxy66fPm10O8bI4zXEp7jzgGtg/0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-216--CAnWxERNqOy0_uX_Wk_PQ-1; Fri, 08 Jan 2021 04:43:53 -0500 X-MC-Unique: -CAnWxERNqOy0_uX_Wk_PQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1657F1005D5D; Fri, 8 Jan 2021 09:43:51 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-111.ams2.redhat.com [10.36.113.111]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3902460C5F; Fri, 8 Jan 2021 09:43:48 +0000 (UTC) Subject: chocolatey.org instability [was: OvmfPkg/PlatformCI/.azurepiplines: Use stable release of QEMU] To: devel@edk2.groups.io, michael.d.kinney@intel.com, =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= Cc: Sean Brogan , Bret Barkelew , Liming Gao , "Justen, Jordan L" , Ard Biesheuvel References: <20201125050758.1507-1-michael.d.kinney@intel.com> <20201125050758.1507-4-michael.d.kinney@intel.com> From: "Laszlo Ersek" Message-ID: <4b3e1777-d1e9-0512-9bb9-334b1e9b64d8@redhat.com> Date: Fri, 8 Jan 2021 10:43:47 +0100 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 11/25/20 17:23, Michael D Kinney wrote: > Hi Phillippe, > > We use choco command to install qemu for Windows, and as of this morning, the 20201124 > release has not been published on choco. > > https://chocolatey.org/packages/Qemu > > Once it is published on choco, we can test it and if it passes, we can revert this > change and resume using the latest qemu release. Hijacking the thread a little -- keeps failing because chocolatey.org keeps returning "(520) Origin Error" to the choco install qemu --version=2020.08.14 command. Note that this particular version of the QEMU "choco" package still exists: https://chocolatey.org/packages/Qemu/2020.08.14 Can we make ourselves independent of "chocolatey.org" somehow? Every such external dependency can block all merges. Perhaps we should create another repository under the tianocore organization on github, and keep Windows binaries for QEMU there. I'm quite displeased with the stability issues we've recently seen in the edk2 CI environment recently, and (AFAICT) none of those have been our fault. What's *really* annoying is that, when a maintainer wants to work around such an env issue, to proceed with a particular merge, the maintainer gets to post a separate patch to edk2-devel first, and wait for review. That means a possibly *multi-day* delay for merging an already reviewed patch series. This is terrible. Laszlo