search

openprov / interop-test-harness

Interoperability test harness for the Southampton Provenance Suite.
MIT License
1 stars 2 forks source link

Travis CI terminates test run takes longer than 120 minutes #13

Open mikej888 opened 9 years ago

mikej888 commented 9 years ago

When running a set of tests, a Travis CI test run can terminate with the following warning, if the run takes longer than 2 hours:

Your test run exceeded 120 minutes. 

One possible solution is to split up your test run.

See, for example log.txt

As for #12, a possible solution is to partition up the tests into smaller jobs (e.g. using the Travis build matrix for parallelisation as described in #9).

LuxoftAKutsan commented 8 years ago

@mikej888 Hi do you know is 120 minutes is restriction only for free Travis?

Is this restriction applicable only for tests run? Or full travis job run (build, run and coverage collect)?

mikej888 commented 8 years ago

Customizing the Build comments that:

Travis CI has specific time limits for each job, and will stop the build and and add an error message to the build log in the following situations:

A job takes longer than 50 minutes on travis-ci.org A job takes longer than 120 minutes on travis-ci.com

which seems to have changed as I used travis-ci.org and got 120 minutes.

According to that same page

There is no timeout for a build; a build will run as long as all the jobs do as long as each job does not timeout.

A "build" (in Travis CI terms) is composed of N jobs where each job corresponds to a specific configuration in the build matrix e.g. the build matrix for this repository would spawn a Python 2.7 job and a Python 3.4 job.

So it looks like the timeout for a job applies to everything in that job e.g. building the software, running the tests and collecting coverage.