From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web12.2627.1583782662301060888 for ; Mon, 09 Mar 2020 12:37:42 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=X0Ks0m+c; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1583782661; 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=sr3ox4Pp++06DtgYUzPLug5KWsNfhJBexX2qbIGqiao=; b=X0Ks0m+cPe5F6psNKgeS487gV86V3628D4APsY1KLHlfLBSzj2T9iFqrRsZeSw/H1FYRYY qE9sozEbPiJMIepfLuH+GoGovlr0yOXabrlPUJvlCNGwDRekP3T+us7BCGoOHCHDhlSOIk wl9BZ4Vc7PPlZZRe5OXg3hueAUr1eYA= 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-31-aIvsa_BONrS3am7vqsSQdA-1; Mon, 09 Mar 2020 15:37:37 -0400 X-MC-Unique: aIvsa_BONrS3am7vqsSQdA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 3A3B88018C6; Mon, 9 Mar 2020 19:37:36 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-76.ams2.redhat.com [10.36.116.76]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9686588859; Mon, 9 Mar 2020 19:37:34 +0000 (UTC) Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master From: "Laszlo Ersek" To: "Kinney, Michael D" , "devel@edk2.groups.io" , "sean.brogan@microsoft.com" , Bret Barkelew , "Gao, Liming" Cc: "Leif Lindholm (Nuvia address)" , Andrew Fish References: <01473986-a0f7-6143-6f81-63611f1f6b00@redhat.com> Message-ID: Date: Mon, 9 Mar 2020 20:37:33 +0100 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: <01473986-a0f7-6143-6f81-63611f1f6b00@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 03/09/20 20:29, Laszlo Ersek wrote: > mergify.io didn't respond to my ticket They have gotten back to me since; quote: On 03/09/20 14:10, Mehdi Abaakouk wrote: > We are aware of the issue and working on a fix. We recently implement > a Github recommendation about caching Github API HTTP call > (https://developer.github.com/v3/#conditional-requests). > > In some case, like yours, we query Github for retrieving check-runs > with the conditional-requests mechanism and it tells us our cache is > up to date while it's not. > > We have an almost ready change that will detect this case and > invalidate manual our cache. > > In the meantime we have disable this cache. and: On 03/09/20 16:06, Julien Danjou wrote: > This was a caching issue on our side with GitHub. > We resolved this earlier today, so you shouldn't see this kind of > "lag" anymore. My faith in mergify.io is restored, at least. I'm still worried that we're using a system-under-development for gating reviewed and CI-clean patches. Thanks Laszlo