Skip to content

Commit 4175c7d

Browse files
committed
update readme
1 parent 630945f commit 4175c7d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -329,7 +329,7 @@ Tests are also run for every pull request, courtesy [Travis CI](https://travis-c
329329
You might face [build timeout issue on Travis](https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received) if runner takes more than 10 minutes to run tests.
330330

331331
There are 2 possible ways to solve this problem:
332-
1. Run a script which does `console.log` every 1-2 minutes. This will output to console and hence avoid Travis buildtimeout
333-
2. Use `travis_wait` function provided by Travis-CI. prefix `browserstack-runner` by `travis-wait`
332+
1. Run a script which does `console.log` every 1-2 minutes. This will output to console and hence avoid Travis build timeout
333+
2. Use `travis_wait` function provided by Travis-CI. You can prefix `browserstack-runner` command by `travis-wait` in your `travis.yml` file
334334

335-
We would recommend using `travis_wait` function. It also allows you to configure wait time (ex: `travis_wait 20 browserstack-runner` this will extend wait time to 20 minutes). Read more about `travis_wait` [here](https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received)
335+
We would recommend using `travis_wait` function. It also allows you to configure wait time (ex: `travis_wait 20 browserstack-runner`, this will extend wait time to 20 minutes). Read more about `travis_wait` [here](https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received)

0 commit comments

Comments
 (0)