They run once in 6 times (or 7 times, it is configurable).
This is to make an average travis run fast, but still be able to run the full
test once in a while.
I think we should be increasing the number of such additional tests, but
probably not run them overtime.
On 11-Jun-2015, at 3:04 pm, Raja
Hi Abhi,
The last four jobs always complete within secs and doesnt run anyof the
tests listed for those jobs. If they are not required, can you please
remove them?
~Rajani
On Thu, Jun 11, 2015 at 12:10 PM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:
> It appears travis timed ou
It appears travis timed out even before hitting any testing.
“"
Installing some python packages:
/home/travis/build.sh: line 108: 2310 Terminated travis_jigger $!
$timeout $cmd
install
1262.91s$ ./tools/travis/install.sh
“”
Could be because of a transient issue. If it persists some
Hi,
There are test case failures due to timeout, below is the message.
'Your test run exceeded 50 minutes. '
travis-ci job info.
https://travis-ci.org/jayapalu/cloudstack/builds/66205220
Can some one look at travis-ci.
Thanks,
Jayapal