<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">-j and —threads are the same flag. The problem is passing it twice with two different values. I am sort of surprised OptionParser let that past.</div> <br> <div id="bloop_sign_1474487591758140160" class="bloop_sign"></div> <br><p class="airmail_on">On September 21, 2016 at 2:33:48 AM, Renato Golin via llvm-dev (<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>On 21 September 2016 at 01:33, Chris Matthews <chris.matthews@apple.com> wrote:<br>> I think every job should define those or use the LNT default of 1,1. The<br>> validity of compile time and exec time metrics is in question if the job is<br>> loaded incorrectly, so it makes sense to me to not allow that -j to get<br>> passed through.<br><br>The job's default *is* -j1. But we pass -jN to the other steps<br>(compiling Clang, for instance).<br><br>We also pass -jN to LNT, because that means both build and execute in one go.<br><br>I'll change the buildbots to pass both explicitly in nt_flags, and<br>will also change the builder to not pass -j in any case.<br><br>But if users should not be passing -jN, but instead --threads and<br>--build-threads directly, than I think we should make it into an error<br>in LNT, no?<br><br>cheers,<br>--renato<br>_______________________________________________<br>LLVM Developers mailing list<br>llvm-dev@lists.llvm.org<br>http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br></div></div></span></blockquote></body></html>