From: "Sean" <sean.brogan@microsoft.com>
To: Laszlo Ersek <lersek@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Leif Lindholm (Nuvia address)" <leif@nuviainc.com>,
Andrew Fish <afish@apple.com>
Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master
Date: Sun, 8 Mar 2020 19:21:54 +0000 [thread overview]
Message-ID: <DM5PR2101MB0917331518727AAAA879EC22E1E10@DM5PR2101MB0917.namprd21.prod.outlook.com> (raw)
Laszlo - Added comment to your PR.
@Mike Kinney (michael.d.kinney@intel.com) who has mergify permission?
I tried to add comment "@Mergifyio refresh" to the PR but since I don't have "command" permission it was rejected. I am happy to look at mergify a little closer if you give me access.
>From the checks status page it is showing that mergify doesn't think the devops builds completed successfully.
Thanks
Sean
-----Original Message-----
From: Laszlo Ersek <lersek@redhat.com>
Sent: Sunday, March 8, 2020 4:13 AM
To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>; Sean Brogan <sean.brogan@microsoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>; Gao, Liming <liming.gao@intel.com>
Cc: Leif Lindholm (Nuvia address) <leif@nuviainc.com>; Andrew Fish <afish@apple.com>
Subject: [EXTERNAL] Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master
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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftianocore%2Fedk2%2Fpull%2F427&data=02%7C01%7Csean.brogan%40microsoft.com%7Cc2d5483ac15949aefeee08d7c3519fe3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637192627654992493&sdata=ltXl9bU2iCpDE6IoVVuLJXZKb2IUu2FriR863eSXzoE%3D&reserved=0
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftianocore%2Fedk2%2Fpull%2F428&data=02%7C01%7Csean.brogan%40microsoft.com%7Cc2d5483ac15949aefeee08d7c3519fe3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637192627654992493&sdata=0QNlw90PQtaZecULwMdmm9UV6f07tqZ0aSirWFI%2B6oo%3D&reserved=0
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftianocore%2Fedk2%2Fpull%2F430&data=02%7C01%7Csean.brogan%40microsoft.com%7Cc2d5483ac15949aefeee08d7c3519fe3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637192627654992493&sdata=OJiR%2FjNIG%2FzcCNZ8v17dGvyhOyuz542llhMMnzpp1pE%3D&reserved=0
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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.githubstatus.com%2F&data=02%7C01%7Csean.brogan%40microsoft.com%7Cc2d5483ac15949aefeee08d7c3519fe3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637192627654992493&sdata=5KOBWohxQzZnLtBDQd0M3KzemPSx6ilz7An5QXU1uUA%3D&reserved=0
"All Systems Operational"
- https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.notion.so%2FMergify-Status-Page-7803a762235d4ee6bed1f9976d17bd83&data=02%7C01%7Csean.brogan%40microsoft.com%7Cc2d5483ac15949aefeee08d7c3519fe3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637192627654992493&sdata=X5RFNQxdKJW0aO5gWtqaSdds%2Fvvx%2B2Ly5LCinimhbjE%3D&reserved=0
"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
next reply other threads:[~2020-03-08 19:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 19:21 Sean [this message]
2020-03-08 19:53 ` [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master Michael D Kinney
2020-03-09 19:29 ` Laszlo Ersek
2020-03-09 19:32 ` Laszlo Ersek
2020-03-09 22:00 ` Michael D Kinney
2020-03-09 19:37 ` Laszlo Ersek
2020-03-09 20:06 ` Laszlo Ersek
2020-03-09 21:44 ` Michael D Kinney
2020-03-10 7:53 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2019-11-12 2:55 Michael D Kinney
2019-11-12 8:56 ` [edk2-devel] " Laszlo Ersek
2019-11-12 19:50 ` Michael D Kinney
2019-11-12 19:52 ` Michael D Kinney
2019-11-13 7:56 ` Laszlo Ersek
2019-11-13 8:57 ` Laszlo Ersek
2019-11-13 16:23 ` Michael D Kinney
2019-11-13 17:03 ` Laszlo Ersek
2019-11-26 8:23 ` Laszlo Ersek
2019-11-27 19:03 ` Michael D Kinney
2019-11-28 12:00 ` Laszlo Ersek
2019-12-02 19:55 ` Michael D Kinney
2019-12-03 8:56 ` Laszlo Ersek
2019-12-03 17:07 ` Michael D Kinney
2019-12-03 20:39 ` Laszlo Ersek
2019-12-06 11:02 ` Laszlo Ersek
2019-12-06 11:07 ` Laszlo Ersek
2020-01-02 14:42 ` Philippe Mathieu-Daudé
2020-01-02 18:36 ` Michael D Kinney
2020-01-06 14:58 ` Philippe Mathieu-Daudé
2020-01-03 13:29 ` Laszlo Ersek
2020-01-06 17:29 ` Laszlo Ersek
2020-01-06 18:17 ` Michael D Kinney
2020-01-07 9:00 ` Laszlo Ersek
2020-01-09 21:30 ` Laszlo Ersek
2020-01-09 21:37 ` Michael D Kinney
2020-01-10 10:51 ` Laszlo Ersek
2020-03-08 11:12 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM5PR2101MB0917331518727AAAA879EC22E1E10@DM5PR2101MB0917.namprd21.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox