<div dir="ltr">Hi,<div>   I'm looking for some suggestions on debugging pre-merge test failures that look irrelevant.</div><div> </div><div>   Two examples with links (while `ninja check-all` passed for the patch, although the <span style="color:rgb(0,0,0);font-family:Consolas,"Deja Vu Sans Mono","Bitstream Vera Sans Mono",monospace;font-size:13.3px">DLLVM_ENABLE_PROJECTS</span> doesn't necessarily cover the subprojects that fail)</div><div>   1) This is caused by stale cmake configurations, as indicated by the error.</div><div>        <a href="https://buildkite.com/llvm-project/premerge-checks/builds/68728#6abfb9c3-e82d-4bbf-835b-551344e469c5/31-46">Link of build artifact</a>. </div><div>        Sync up to pick up new cmake configurations resolved the error.</div><div><br></div><div>   2) <a href="https://buildkite.com/llvm-project/premerge-checks/builds/69795#22733c7d-1ef1-488d-ad08-d77542b0d7e0">Link of build artifact</a></div><div>     </div><div>       Test failed with error<br clear="all"><div>       </div><pre id="gmail-paste-textbox" class="gmail-span12 gmail-code-container gmail-linenums gmail-prettyprint" style="padding:2px 2px 2px 25px;font-size:12px;color:rgb(51,51,51);border-radius:0px;margin-top:0px;margin-bottom:18px;margin-left:20px;line-height:18px;background-color:rgb(245,245,245);border:1px solid rgb(136,136,136);white-space:pre-wrap;word-break:break-all;width:940px"><ol class="gmail-linenums" style="padding:0px;margin:0px 0px 0px 25px;list-style-position:initial;display:inline-block"><li class="gmail-L0" style="line-height:18px;list-style-type:decimal"><span class="gmail-typ" style="color:rgb(102,0,102)">Failed</span><span class="gmail-pln" style="color:rgb(0,0,0)"> </span><span class="gmail-typ" style="color:rgb(102,0,102)">Tests</span><span class="gmail-pln" style="color:rgb(0,0,0)"> </span><span class="gmail-pun" style="color:rgb(102,102,0)">(</span><span class="gmail-lit" style="color:rgb(0,102,102)">1</span><span class="gmail-pun" style="color:rgb(102,102,0)">):</span></li><li class="gmail-L1" style="line-height:18px;background:rgb(238,238,238);list-style-type:decimal"><span class="gmail-pln" style="color:rgb(0,0,0)">  LLVM </span><span class="gmail-pun" style="color:rgb(102,102,0)">::</span><span class="gmail-pln" style="color:rgb(0,0,0)"> </span><span class="gmail-typ" style="color:rgb(102,0,102)">Bindings</span><span class="gmail-pun" style="color:rgb(102,102,0)">/</span><span class="gmail-typ" style="color:rgb(102,0,102)">Go</span><span class="gmail-pun" style="color:rgb(102,102,0)">/</span><span class="gmail-pln" style="color:rgb(0,0,0)">go</span><span class="gmail-pun" style="color:rgb(102,102,0)">.</span><span class="gmail-pln" style="color:rgb(0,0,0)">test</span></li></ol></pre><div>      I didn't find other information in the log that might help.</div><div><br></div><div>     There is a <a href="https://github.com/google/llvm-premerge-checks/blob/main/docs/playbooks.md">playbook</a> yet I'm wondering if there are more lightweight procedures besides restarting build (e.g., looking at a continuous build dashboard for tests that might already fail or might be flaky before the patch) to debug tests that look irrelevant.</div><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div><font color="#555555" face="sans-serif" size="2">Thanks,</font></div><div><font color="#555555" face="sans-serif" size="2">Mingming</font></div></div></div></div></div></div></div></div>