Skip to content

Conversation

@Leemoonsoo
Copy link
Member

What is this PR for?

Recent Travis CI build is failing with

The log length has exceeded the limit of 4 Megabytes (this usually means that test suite is raising the same exception over and over).

The build has been terminated.

What type of PR is it?

Improvement

Todos

  • - Update .travis.yml to use build matrix

Is there a relevant Jira issue?

How should this be tested?

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update? no
  • Is there breaking changes for older versions? no
  • Does this needs documentation? no

@prabhjyotsingh
Copy link
Contributor

Also how about;

env:
  global:
  - TERM=dumb

read that on stackoverflow, but couldn't find much doc related to it.
or -Dinvoker.debug=false with mvn command ?

@Leemoonsoo Leemoonsoo force-pushed the build_matrix branch 2 times, most recently from b414d72 to 193dcd2 Compare January 12, 2016 23:41
@Leemoonsoo Leemoonsoo changed the title [WIP] Improve travis build script Improve travis build script Jan 13, 2016
@Leemoonsoo
Copy link
Member Author

Now .travis.yml creates each build job for each build profile instead of run every build profile in a single job. So output message is splitted into different build job.

@minahlee
Copy link
Member

+1 let's merge it

@Leemoonsoo
Copy link
Member Author

While every CI test is failing, i'm merging this patch as a hotfix.

@asfgit asfgit closed this in 0c42f43 Jan 13, 2016
@elbamos
Copy link
Contributor

elbamos commented Jan 13, 2016

+1

asfgit pushed a commit that referenced this pull request Feb 12, 2016
### What is this PR for?
While investigating CI failure with PR #706, I noticed that we were running all tests in each of 6 jobs in the test matrix.

It seems we have accidentally switched back to running all tests even with older versions of Spark. (from PR #626

Filtering out interpreter tests for these runs help make test jobs faster (~30%) and also reduce the chance that an interpreter test might intermittently fail, thus hopefully improve CI reliability.

Also changing Spark 1.2.1 to 1.2.2 (last 1.2.x release)

### What type of PR is it?
Improvement

### Todos
* [x] - Travis CI yml changes

### Is there a relevant Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-665

### How should this be tested?
Run Travis CI

### Screenshots (if appropriate)
N/A

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: Felix Cheung <felixcheung_m@hotmail.com>

Closes #708 from felixcheung/testprofile and squashes the following commits:

ac3bd72 [Felix Cheung] fix project list
b0c8b9b [Felix Cheung] add spark tests
27d57fe [Felix Cheung] fix project list
cd0cb97 [Felix Cheung] test project list for older spark versions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants