write stdout/stderr to a log file under the deploy directory

[gregcaporaso]

It would be convenient for debugging failed runs if stdout/stderr were written to a log file under the deploy directory. Currently I think if you lose stdout/stderr you're out of luck.

[pdmars]

OK. I think that's probably a good idea. I typically try to avoid adding additional options/stuff when things are already possible within an environment, but I can understand many users don't know to tack on "2>&1 | tee output.log" to the command. Should it be an option to enable it? Or enable by default and include an option to suppress it?

[gregcaporaso]

I say enable by default and allow the user to suppress, but whatever you
prefer is fine with me.

On Tue, Apr 30, 2013 at 8:42 AM, Paul [email protected] wrote:

OK. I think that's probably a good idea. I typically try to avoid adding
additional options/stuff when things are already possible within an
environment, but I can understand many users don't know to tack on "2>&1 |
tee output.log" to the command. Should it be an option to enable it? Or
enable by default and include an option to suppress it?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/28#issuecomment-17235169
.

[pdmars]

Sounds good.