<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Mateusz,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I wouldn’t worry too much about the failed build. I took a peek and it looks like the failures are mostly in places very unrelated to your patch. If your own testing shows no problems, it’s very likely you’re fine.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regarding lack of response, this is unfortunately more common than it should be. Our recommended practice—and I’m surprised we don’t say anything on the website—is to add a “ping” comment to your review, maybe once a week. This can “bump”
it up in someone’s to-be-reviewed list; if nothing else, there’s another email to the list that will hopefully catch someone’s attention.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Good luck,<o:p></o:p></p>
<p class="MsoNormal">--paulr<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cfe-commits <cfe-commits-bounces@lists.llvm.org>
<b>On Behalf Of </b>stryku_t via cfe-commits<br>
<b>Sent:</b> Thursday, May 26, 2022 4:20 PM<br>
<b>To:</b> cfe-commits@lists.llvm.org<br>
<b>Subject:</b> Call for an assistance pushing patch review forward<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi,<br>
<br>
Some time ago I submitted a Clang patch for review: <a href="https://urldefense.com/v3/__https:/reviews.llvm.org/D123532__;!!JmoZiZGBv3RvKRSx!50L_QF_AnQxi9DrDNMB3pgj_sW2uyIdYcirpjiXNxp8UH_lJAzfKNPpW0955SGkAcIrq5WqRSR4bklmZ1pLw2HtMjdE$">
https://reviews.llvm.org/D123532</a><br>
<br>
It's been some time and I can't make progress with it.<br>
I'm aware that there is failed build. But, as I mentioned in one of the comments, I can't reproduce it locally.<br>
Tried to reach out to the people mentioned in the review, but I struggle getting answers.<br>
At this point I'm not sure if I'm doing something wrong or people are just busy. Should tag different people? Different project? Am I expected to figure out failed builds on my own before someone will review the changes?<br>
<br>
Could someone from the community please assist me how for move forward with this patch? Also, I'd be grateful if there's someone who can hint me how to reproduce failed builds locally or using some CI server.<br>
<br>
Thanks in advance!<br>
<br>
Best regards,<br>
Mateusz Janek<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>