<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I really want this feature. It may not be clean, but would save a lot of time in practice. However...<div><br><div><div>On Oct 24, 2013, at 10:35 PM, Alp Toker <<a href="mailto:alp@nuanti.com">alp@nuanti.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;">lit shell tests and compiled unit tests are both supported. At the moment, the cache is implemented by scanning and modifying test source mtimes directly. This hasn't caused trouble but the technique could be refined in future to store test failures in a separate cache file if needed.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote></div><br></div><div>This doesn’t feel right. I don’t think it will personally cause me any grief, but seems like someone or their tools will be confused. If others think it’s ok, I won’t object. I just don’t want to accept the patch until others review this aspect.</div><div><br></div><div>-Andy</div></body></html>