<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 5 Jan 2021, at 1:33 AM, Barry Smith <<a href="mailto:bsmith@petsc.dev" class="">bsmith@petsc.dev</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""> For packages that are built after PETSc configure (and or install is done) slepc, hpddm etc we've traditional saved the output in its own file stashed away somewhere. <br class=""><br class=""> For the CI this is driving me nuts because when they fail the output is essentially "lost" and thus it is impossible to determine what has gone wrong. <br class=""><br class=""> I have started to directly output in the same stream as the PETSc compiles to make debugging much easier. Generally the packages are relatively small and don't have a huge amount of output when compiling correctly. I did it for PETSc4py and SLEPc (slepc4py is a mystery yet how it get's hidden in slepc). <br class=""></div></div></blockquote><div><br class=""></div><div>I guess we could change the redirect rule here <a href="https://gitlab.com/slepc/slepc/-/blob/master/config/packages/slepc4py.py#L53" class="">https://gitlab.com/slepc/slepc/-/blob/master/config/packages/slepc4py.py#L53</a>?</div><div>But we’d need to check whether slepc4py is built with --download-slepc --download-slepc-configure-arguments="--download-slepc4py” (inside PETSc) or simply --download-slepc4py (inside SLEPc).</div><div><br class=""></div><div>I’m in favour of having a single file because it can be quite nightmarish to ask users for multiple .log files hidden in different folders, but I can understand if we stick with the current approach as well.</div><div><br class=""></div><div>Thanks,</div><div>Pierre</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""> Are there any large downsides to this plan?<br class=""><br class=""> Barry<br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></body></html>