[MDEV-16213] Travis jobs are killed way to often due to time limit Created: 2018-05-18 Updated: 2018-06-29 Resolved: 2018-06-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Tests |
| Fix Version/s: | 10.3.8 |
| Type: | Task | Priority: | Minor |
| Reporter: | Teodor Mircea Ionita (Inactive) | Assignee: | Teodor Mircea Ionita (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
All jobs that are marked with a ! and errored status (different from failed) have been killed by travis due to exceeding the max runtime of 50 minutes:
https://travis-ci.org/MariaDB/server/builds In this case, some parts of big suites like main, rpl and binlog may never get to attended. The solution would be to reconsider the current test suite matrix split inside .travis.yml:
Maybe split big suites like main, innodb. binlog into separe jobs for a start and see the change? I can try that out on my own Travis setup first: |
| Comments |
| Comment by Elena Stepanova [ 2018-05-18 ] |
|
Before doing something big, please make sure it's not a Travis issue. Travis has been misbehaving recently (again), tests on my repo fail either with clear environmental problems, or with obscure timeouts. It happened before and then got resolved on the Travis side. |
| Comment by Teodor Mircea Ionita (Inactive) [ 2018-05-24 ] |
|
All green on my repo: Top three commits: In a gist, stop using clang4, rename GCC_VERSION to CC_VERSION, use same version for both clang and gcc for simplicity and clarity. Split main and rocksdb suites to separate jobs. |
| Comment by Teodor Mircea Ionita (Inactive) [ 2018-06-29 ] |
|
Fixed in 4d637628d34d64183a6fb0962983244680ace167~4...4d637628d34d64183a6fb0962983244680ace167 |