# Long tests fail: No output has been received in the last 10m

**URL:** <https://travis-ci.community/t/long-tests-fail-no-output-has-been-received-in-the-last-10m/5678>\
**Category:** Deployment\
**Tags:** travis-build\
**Created:** [October 25, 2019, 9:42pm UTC](https://travis-ci.community/t/long-tests-fail-no-output-has-been-received-in-the-last-10m/5678 "2019-10-25T21:42:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ceandrade](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/ceandrade/32/2999_2.png) [@ceandrade](https://travis-ci.community/u/ceandrade)\
**Post date:** [October 25, 2019, 9:42pm UTC](https://travis-ci.community/t/long-tests-fail-no-output-has-been-received-in-the-last-10m/5678/1 "2019-10-25T21:42:47Z")

</div>

Hi,

I have a package that have long run tests (more than 30min). Since Travis has this 10min rule, the build never finishes. I read about `travis_wait`, but I’m not sure how to use in my case. This is my .travis.yml:

```auto
language: julia
os:
  - linux
  - osx

julia:
  - 1.2
  - nightly

notifications:
  email: false
git:
  depth: 99999999

matrix:
  allow_failures:
  - julia: nightly

before_install:
  - if ["$TRAVIS_OS_NAME" = "osx"]; then brew update ; fi

addons:
  apt:
    packages:
      - hdf5-tools
  homebrew:
    packages:
    - hdf5

```

This is the end of the log:

```auto
>> Testing path relink methods (it may take a while)...
Test Summary: | Pass Total
find_block_range() | 19 19
Test Summary: | Pass Total
direct_path_relink!() | 26 26

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

The build has been terminated

```

So, how can I setup Travis to allow long run tests?

Carlos

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [October 26, 2019, 12:27am UTC](https://travis-ci.community/t/long-tests-fail-no-output-has-been-received-in-the-last-10m/5678/2 "2019-10-26T00:27:56Z")

</div>

> [@Use \`travis\_wait\` but still see the output](https://travis-ci.community/t/use-travis-wait-but-still-see-the-output/5647/2):
>
> Consider making that build report on its progress. Not outputting anything is awful UX because you can’t tell if anything’s happening or it’s stuck (which is bad because if it’s stuck, you are wasting your time waiting for it; and you also have no idea where exactly it’s stuck to be able to fix that). Travis’ auto termination is there specifically to kill stuck commands – for our mutual benefit, as per above. There is no supported way. travis\_wait saves output to a log file and prints it all …