Kenneth, yes, for the configure and build steps I have the output in the log filed (sorry for the confusion before), but I don't see anything for the test step. For example, for both Tcl and Perl the last thing I see is:
== 2017-01-30 17:55:58,057 easyblock.py:2274 INFO Running method test_step part of step test If the test hangs (as happened in both cases for me) I have no clue what is going wrong. DV On Jan 31 2017, at 4:09 am, Kenneth Hoste <[email protected]> wrote: Hi Davide, On 30/01/2017 23:08, Vanzo, Davide wrote: Hello world, I would find quite useful to have an option (or maybe make it a default behavior) to get the full raw standard output and error from whatever EB is running (make, test, etc.). For example, while installing Tcl it was hanging at the test section. After trying manually, I realized it was the httpd test that was hanging because of the iptables rules on that port. If I would have had access to the raw output I could have figured it out without having to redo the test manually outside EB. This would be even more useful when developing an easyconfig or easyblock. Have I missed the option or is it something that should be implemented on EB? This output should be available in the log file that EasyBuild collects? The location of the (temporary) log file is printed at the start of EB. With the hanging Tcl installation, you should be able to just dive into the log file after hitting Ctrl-C? If needed, you could pass --debug to get a debug log, but the info you're looking for should be there by default already... regards, Kenneth Thanks! -- Davide Vanzo, PhD Application Developer Adjunct Assistant Professor of Chemical and Biomolecular Engineering Advanced Computing Center for Research and Education (ACCRE) Vanderbilt University - Hill Center 201 (615)-875-9137 www.accre.vanderbilt.edu<http://www.accre.vanderbilt.edu>
