# No output logged when using \`travis\_wait\` command

**URL:** <https://travis-ci.community/t/no-output-logged-when-using-travis-wait-command/1909>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [January 18, 2019, 4:15pm UTC](https://travis-ci.community/t/no-output-logged-when-using-travis-wait-command/1909 "2019-01-18T16:15:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [January 18, 2019, 4:34pm UTC](https://travis-ci.community/t/no-output-logged-when-using-travis-wait-command/1909/2 "2019-01-18T16:34:05Z")

</div>

This has nothing to do with the use of `travis_wait`. You are setting the `errexit` option on the bash:

> <https://github.com/bitcoin/bitcoin/blob/12b30105fc59daef2ae2fd8f81be1159ca68f94a/.travis.yml#L49>

and this means that any command that exits with a nonzero status will terminate the build _immediately_.

`travis_wait` does not have a chance to dump the logs it is collecting.

---

_[View the full topic](https://travis-ci.community/t/no-output-logged-when-using-travis-wait-command/1909)._