From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.120])
 by mx.groups.io with SMTP id smtpd.web11.31530.1583665964188713460
 for <devel@edk2.groups.io>;
 Sun, 08 Mar 2020 04:12:44 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=B2H1fsrL;
 spf=pass (domain: redhat.com, ip: 207.211.31.120, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1583665963;
	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=ga/+bZlTMWxgUqyE+2pjvbP4AuJkjq8+P6IW0rMH3Wk=;
	b=B2H1fsrLER83/t06uzeBH0aLkNadXIM/voFCAmpN0a249rtCwDYMs3Ea9VPZ9f3Ae4K05T
	nUBXGNQCgnbtZwf5vlHK5JFAcegr72hjIL0aPU8VsBUpn8nao682WDTrrESxw4UfcMYj+Z
	5NP09Y5VWjD+fyJ5iV03I8aTCzp9DpU=
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-423-7_lfP0fLODyQ3734Aa-DOQ-1; Sun, 08 Mar 2020 07:12:39 -0400
X-MC-Unique: 7_lfP0fLODyQ3734Aa-DOQ-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 ED9F51005509;
	Sun,  8 Mar 2020 11:12:37 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-62.ams2.redhat.com [10.36.116.62])
	by smtp.corp.redhat.com (Postfix) with ESMTP id D9E1360BF7;
	Sun,  8 Mar 2020 11:12:35 +0000 (UTC)
Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
 Sean Brogan <sean.brogan@microsoft.com>,
 Bret Barkelew <Bret.Barkelew@microsoft.com>,
 "Gao, Liming" <liming.gao@intel.com>
References: <E92EE9817A31E24EB0585FDF735412F5B9E173A1@ORSMSX113.amr.corp.intel.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Cc: "Leif Lindholm (Nuvia address)" <leif@nuviainc.com>,
 Andrew Fish <afish@apple.com>
Message-ID: <cc701ccc-f3d7-1ad6-5144-7f673b4a69f8@redhat.com>
Date: Sun, 8 Mar 2020 12:12:35 +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: <E92EE9817A31E24EB0585FDF735412F5B9E173A1@ORSMSX113.amr.corp.intel.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Language: en-US
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

On 11/12/19 03:55, Michael D Kinney wrote:

> Please let us know if there are any questions about this
> change in the development process.

What is the recommended way to report issues with the mergify (not CI)
infrastructure?

Mergify hasn't been picking up ready-to-merge branches (with CI passed
and the "push" label set).

  https://github.com/tianocore/edk2/pull/427
  https://github.com/tianocore/edk2/pull/428
  https://github.com/tianocore/edk2/pull/430

I've filed a ticket with github (#592107) and emailed
<support@mergify.io> too. But, the github ticket number doesn't seem
useful (there is not a "case" that I could overview, or share with
others, using the ticket number), and mergify.io don't seem to have
generated even a ticket number for me.

Both github.com and mergify.io claim to have 100% service level at the
moment:

- https://www.githubstatus.com/

  "All Systems Operational"

- https://www.notion.so/Mergify-Status-Page-7803a762235d4ee6bed1f9976d17bd83

  "Dashboard Operational", "Engine Operational"

In the absence of github / mergify feedback, it would be nice if at
least stewards could manually merge such topic branches that have passed
CI.

Thanks
Laszlo