You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering the following scenario with travis CI right now: 'stack test' takes a long time to finish and it redirects output to a log file. Travis kills process because it has no output for some time:
No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.
Am i missing something or there is currently no way of redirecting output from stack to a stdout? Wouldn't it be nice to have this?
The text was updated successfully, but these errors were encountered:
I wonder if stack --verbose test would be enough for travis
Also, I've noticed that the verbosity in the output may be different depending if it is a multi-package project (less verbose than single-package)
for multi-package project you can try doing it individually:
I'm encountering the following scenario with travis CI right now: 'stack test' takes a long time to finish and it redirects output to a log file. Travis kills process because it has no output for some time:
Am i missing something or there is currently no way of redirecting output from stack to a stdout? Wouldn't it be nice to have this?
The text was updated successfully, but these errors were encountered: