<div dir="ltr">TJ et al,<div><ul><li>I think the commit to CMBDashboard yesterday was the right fix.</li><li>However, ES master failed to build on Praxis last night.</li><li>But this time the problem is that Praxis is out of disk space. That's right, we've managed to fill the 1TB drive.</li><li>I presume there's alot we can delete on Praxis. I started by emptying the trash, which is at 20GB and counting...</li></ul></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 18, 2017 at 2:49 PM, T.J. Corona <span dir="ltr"><<a href="mailto:tj.corona@kitware.com" target="_blank">tj.corona@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Thanks for the info and the fix John!<br><br><div id="m_4035644309350019884AppleMailSignature">Sent from my iPhone</div><div><div class="h5"><div><br>On Nov 18, 2017, at 1:06 PM, John Tourtellott <<a href="mailto:john.tourtellott@kitware.com" target="_blank">john.tourtellott@kitware.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Change committed to cmake files in CMBDashboard repo. Fingers crossed...<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 18, 2017 at 11:12 AM, John Tourtellott <span dir="ltr"><<a href="mailto:john.tourtellott@kitware.com" target="_blank">john.tourtellott@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Oh, and to answer your original question, TJ, the console logs from nightly builds on Praxis can be found at C:\dashboards\nightly\logs</div><div class="m_4035644309350019884HOEnZb"><div class="m_4035644309350019884h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 18, 2017 at 11:06 AM, John Tourtellott <span dir="ltr"><<a href="mailto:john.tourtellott@kitware.com" target="_blank">john.tourtellott@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hmmm, the upload script seems to be looking at a different directory than where the build is done on Praxis. Ben made some changes to CMBDashboard yesterday to shorten path lengths again (I presume), but apparently something got missed. Some places were changed to a folder name "bme", others use "build-es". I presume that "bme" is the new one and should be used. I don't have time right now, but unless anyone objects, I'll double check this afternoon and update CMBDashboard (CTEST_BINARY_DIRECTORY in praxis-cmb-es-master.cmake).<div><div><br></div></div></div><div class="m_4035644309350019884m_-2157313137545480624HOEnZb"><div class="m_4035644309350019884m_-2157313137545480624h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 18, 2017 at 10:44 AM, John Tourtellott <span dir="ltr"><<a href="mailto:john.tourtellott@kitware.com" target="_blank">john.tourtellott@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I am 90% sure that the nightly's on Praxis redirect the console to log files. So if you can find the log file on Praxis...</div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_4035644309350019884m_-2157313137545480624m_-416085156349407152h5">On Sat, Nov 18, 2017 at 9:16 AM, TJ Corona <span dir="ltr"><<a href="mailto:tj.corona@kitware.com" target="_blank">tj.corona@kitware.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_4035644309350019884m_-2157313137545480624m_-416085156349407152h5"><div style="word-wrap:break-word;line-break:after-white-space"><div>Hi all,</div><div><br></div><div>I do not understand why praxis did not post an ES master build last night. The <a href="https://open.cdash.org/testDetails.php?test=601610533&build=5147148" target="_blank">packaging test succeeded</a>, and the release build posted. How would I look into why the build didn’t upload?</div><div><br></div><div>Sincerely,</div><div>T.J.</div><br><div>
<div style="word-wrap:break-word"><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">Thomas J. Corona, Ph.D.<br>Kitware, Inc.<br>Senior R&D Engineer<br><a href="https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g">21 Corporate Drive</a><br><a href="https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g">Clifton Park, NY 12065</a>-8662<br>Phone: <a href="tel:(518)%20881-4443" value="+15188814443" target="_blank">518-881-4443</a></div></div>
</div>
<br></div><br></div></div>______________________________<wbr>_________________<br>
Smtk-developers mailing list<br>
<a href="mailto:Smtk-developers@smtk.org" target="_blank">Smtk-developers@smtk.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/smtk-developers" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/smtk-developers</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></blockquote></div></div></div></blockquote></div><br></div>