<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Zach,<div class="">Thanks for doing this extra work to make this lower impact for the rest of us. Let’s give it a try and see what happens.</div><div class=""><br class=""></div><div class="">-Mike</div><div class=""><br class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Nov 9, 2017, at 13:37, Zachary Turner <<a href="mailto:zturner@google.com" class="">zturner@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi all, I think I've addressed all the concerns here, and I believe there should be no immediate impact to the current workflow. with that said, I plan to commit this either later today or early tomorrow if there are no other concerns.</div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, Nov 7, 2017 at 12:19 PM Zachary Turner <<a href="mailto:zturner@google.com" class="">zturner@google.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">I tested this out, and AFAICT nothing will change. It will continue to just work if you have it checked out under clang/tests. It's a bit hard to construct this configuration locally since it requires moving some files around, and applying half of a CL here and half of a CL there. But, AFAICT it works.<div class=""><br class=""></div><div class="">I'm happy to send you some patches if you want to try them locally and confirm.</div><div class=""><br class=""></div><div class="">I'd like to print out a CMake warning if it detects the tree under clang/test and just mention that the workflow is deprecated. Any objections?</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Mon, Nov 6, 2017 at 1:49 PM Mike Edwards <<a href="mailto:medwards@apple.com" target="_blank" class="">medwards@apple.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Thank you Zach.</div><div style="word-wrap:break-word" class=""><br class="">
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Nov 6, 2017, at 13:37, Zachary Turner <<a href="mailto:zturner@google.com" target="_blank" class="">zturner@google.com</a>> wrote:</div><br class="m_-5097655787862249898m_-6773414355929158844Apple-interchange-newline"><div class="">I’m going to spend a little time seeing if i can make the change invisible to the bots so they will continue to work as they do today. Will report back after I’ve explored that a bit<br class=""><div class="gmail_quote"><div dir="ltr" class="">On Mon, Nov 6, 2017 at 1:35 PM Mike Edwards <<a href="mailto:medwards@apple.com" target="_blank" class="">medwards@apple.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><div class="gmail_quote"><div class="">I'm honestly not opposed to this idea. It just seems a shame to do this for purely logistical reasons if most people agree that the "right" place for debuginfo-tests is outside of the clang tree. </div></div></div></div></blockquote><div class=""><br class=""></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class="">I totally understand what you are saying here and will just add that sometimes being part of a larger community means being willing to do things, sometimes, not exactly the “right” way, due to logistical reasons. I am not opposed to what you would like to do, I’m just furrowing my brow at the timeframe in which to do it.</div></div></div><div style="word-wrap:break-word" class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class=""><div class="gmail_quote"><div class=""><br class=""></div><div class="">That said, I'd still like to hear from ChrisM and MikeE about why it will take so long, because on the surface it seems like a low-impact move.</div></div></div></div></blockquote><br class=""></div></div><div style="word-wrap:break-word" class=""><div class=""></div><div class="">Past experience has taught me, anything I think is going to be simple and quick to fix, rarely ever turns out that way. While there will be a significant amount of work to change the way our bots work here at Apple, the work is not impossible to accomplish. Given the choice, I would of course prefer an approach such as Paulr has suggested. The ability to run things in parallel for a time provides for a much lower impact change on the entire community. I think this approach may also give us some time to decide where the debuginfo-test should fit in the new mono-repo. It would be a bummer to do the work necessary to make this change, only to discover we would have to do it differently in the not too distant future to accommodate the new mono-repo. </div><div class=""><br class=""></div><div class=""> Zach, I do not want to be a blocker here. I just want to make sure we have explored all of the options to make sure we are not missing a lower impact approach. I also want to make sure we are not doing something that could wait until we migrate to the mono-repo next year.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Mike</div></div></blockquote></div>
</div></blockquote></div><br class=""></div></blockquote></div></blockquote></div>
</div></blockquote></div><br class=""></div></body></html>