You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by Eric Charles <er...@apache.org> on 2016/03/08 11:36:43 UTC

Travis Build flags for tests

Hi there,

I see tests are disabled on Travis.

e.g. From 
https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt

$ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
$ export BUILD_FLAG="package -DskipTests"

Is this on purpose?

Re: Travis Build flags for tests

Posted by Felix Cheung <fe...@hotmail.com>.

In order to minimize duplication, only the first in Travis matrix is running every tests (excluding selenium, which is separate)






On Thu, Mar 10, 2016 at 1:56 AM -0800, "Corneau Damien" <co...@gmail.com> wrote:





I just looked at this PR (
https://github.com/apache/incubator-zeppelin/pull/772) which has CI failing
(1.6 profile only)
And after comparing 1.6 to 1.5, the logs are showing that 1.5 are skipping
tests while 1.6 doesn't (at least in Display systems api)

On Thu, Mar 10, 2016 at 2:22 AM, Felix Cheung <fe...@hotmail.com>
wrote:

> Indeed. There are many variations of intermitted network errors - now we
> are retrying download but I have seen it failing after 3 retries, or
> getting a corrupted partial file and so on. One possibility is to leverage
> Travis' container base run and caching to avoid download of spark bits and
> dependencies in maven...
>
>
>
>
>
>
> On Tue, Mar 8, 2016 at 9:50 PM -0800, "Eric Charles" <er...@apache.org>
> wrote:
>
>
>
>
>
> What are you thinking to: Build time, stability....?
>
> I have seen work to optimize the download of spark.
>
> Travis starts from a clean env which is good but things take time to be
> downloaded and setup.
>
> I guess we have to log each failure which should not occur and tackle
> them. I have seen multiple times such errors which should not occur:
>
> Failed tests:
>
> ZeppelinSparkClusterTest.pySparkDepLoaderTest:167->getSparkVersionNumber:220
> expected:<FINISHED> but was:<ERROR>
>
> ZeppelinSparkClusterTest.pySparkAutoConvertOptionTest:112->getSparkVersionNumber:220
> expected:<FINISHED> but was:<ERROR>
>    ZeppelinSparkClusterTest.basicRDDTransformationAndActionTest:81
> expected:<FINISHED> but was:<ERROR>
>    ZeppelinSparkClusterTest.pySparkTest:90->getSparkVersionNumber:220
> expected:<FINISHED> but was:<ERROR>
>    ZeppelinSparkClusterTest.zRunTest:152 expected:<FINISHED> but
> was:<ERROR>
>
>
> (https://s3.amazonaws.com/archive.travis-ci.org/jobs/111732702/log.txt)
>
> Apparently checkIfServerIsRunning is the cause - maybe the server takes
> time to open the socket...
>
>
> On 08/03/16 19:49, Felix Cheung wrote:
> > I think there are rooms to optimize much more - feel free to propose or
> contribute!
> >
> >
> >
> >
> >
> >
> > On Tue, Mar 8, 2016 at 10:29 AM -0800, "Eric Charles" <er...@apache.org>
> wrote:
> >
> >
> >
> >
> >
> > Makes sense. No need to run tests if a module fails on compilation,
> > format...
> >
> > On 08/03/16 18:52, Felix Cheung wrote:
> >> Right now Travis does a full build first and then run the tests in a
> separate steps.
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Tue, Mar 8, 2016 at 2:36 AM -0800, "Eric Charles" <er...@apache.org>
> wrote:
> >>
> >>
> >>
> >>
> >>
> >> Hi there,
> >>
> >> I see tests are disabled on Travis.
> >>
> >> e.g. From
> >> https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt
> >>
> >> $ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
> >> $ export BUILD_FLAG="package -DskipTests"
> >>
> >> Is this on purpose?
> >>
> >
>

Re: Travis Build flags for tests

Posted by Corneau Damien <co...@gmail.com>.

I just looked at this PR (
https://github.com/apache/incubator-zeppelin/pull/772) which has CI failing
(1.6 profile only)
And after comparing 1.6 to 1.5, the logs are showing that 1.5 are skipping
tests while 1.6 doesn't (at least in Display systems api)

On Thu, Mar 10, 2016 at 2:22 AM, Felix Cheung <fe...@hotmail.com>
wrote:

> Indeed. There are many variations of intermitted network errors - now we
> are retrying download but I have seen it failing after 3 retries, or
> getting a corrupted partial file and so on. One possibility is to leverage
> Travis' container base run and caching to avoid download of spark bits and
> dependencies in maven...
>
>
>
>
>
>
> On Tue, Mar 8, 2016 at 9:50 PM -0800, "Eric Charles" <er...@apache.org>
> wrote:
>
>
>
>
>
> What are you thinking to: Build time, stability....?
>
> I have seen work to optimize the download of spark.
>
> Travis starts from a clean env which is good but things take time to be
> downloaded and setup.
>
> I guess we have to log each failure which should not occur and tackle
> them. I have seen multiple times such errors which should not occur:
>
> Failed tests:
>
> ZeppelinSparkClusterTest.pySparkDepLoaderTest:167->getSparkVersionNumber:220
> expected:<FINISHED> but was:<ERROR>
>
> ZeppelinSparkClusterTest.pySparkAutoConvertOptionTest:112->getSparkVersionNumber:220
> expected:<FINISHED> but was:<ERROR>
>    ZeppelinSparkClusterTest.basicRDDTransformationAndActionTest:81
> expected:<FINISHED> but was:<ERROR>
>    ZeppelinSparkClusterTest.pySparkTest:90->getSparkVersionNumber:220
> expected:<FINISHED> but was:<ERROR>
>    ZeppelinSparkClusterTest.zRunTest:152 expected:<FINISHED> but
> was:<ERROR>
>
>
> (https://s3.amazonaws.com/archive.travis-ci.org/jobs/111732702/log.txt)
>
> Apparently checkIfServerIsRunning is the cause - maybe the server takes
> time to open the socket...
>
>
> On 08/03/16 19:49, Felix Cheung wrote:
> > I think there are rooms to optimize much more - feel free to propose or
> contribute!
> >
> >
> >
> >
> >
> >
> > On Tue, Mar 8, 2016 at 10:29 AM -0800, "Eric Charles" <er...@apache.org>
> wrote:
> >
> >
> >
> >
> >
> > Makes sense. No need to run tests if a module fails on compilation,
> > format...
> >
> > On 08/03/16 18:52, Felix Cheung wrote:
> >> Right now Travis does a full build first and then run the tests in a
> separate steps.
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Tue, Mar 8, 2016 at 2:36 AM -0800, "Eric Charles" <er...@apache.org>
> wrote:
> >>
> >>
> >>
> >>
> >>
> >> Hi there,
> >>
> >> I see tests are disabled on Travis.
> >>
> >> e.g. From
> >> https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt
> >>
> >> $ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
> >> $ export BUILD_FLAG="package -DskipTests"
> >>
> >> Is this on purpose?
> >>
> >
>

Re: Travis Build flags for tests

Posted by Felix Cheung <fe...@hotmail.com>.

Indeed. There are many variations of intermitted network errors - now we are retrying download but I have seen it failing after 3 retries, or getting a corrupted partial file and so on. One possibility is to leverage Travis' container base run and caching to avoid download of spark bits and dependencies in maven...

On Tue, Mar 8, 2016 at 9:50 PM -0800, "Eric Charles" <er...@apache.org> wrote:

What are you thinking to: Build time, stability....?

I have seen work to optimize the download of spark.

Travis starts from a clean env which is good but things take time to be
downloaded and setup.

I guess we have to log each failure which should not occur and tackle
them. I have seen multiple times such errors which should not occur:

Failed tests:
ZeppelinSparkClusterTest.pySparkDepLoaderTest:167->getSparkVersionNumber:220
expected:<FINISHED> but was:<ERROR>
ZeppelinSparkClusterTest.pySparkAutoConvertOptionTest:112->getSparkVersionNumber:220
expected:<FINISHED> but was:<ERROR>
   ZeppelinSparkClusterTest.basicRDDTransformationAndActionTest:81
expected:<FINISHED> but was:<ERROR>
   ZeppelinSparkClusterTest.pySparkTest:90->getSparkVersionNumber:220
expected:<FINISHED> but was:<ERROR>
   ZeppelinSparkClusterTest.zRunTest:152 expected:<FINISHED> but was:<ERROR>

(https://s3.amazonaws.com/archive.travis-ci.org/jobs/111732702/log.txt)

Apparently checkIfServerIsRunning is the cause - maybe the server takes
time to open the socket...

On 08/03/16 19:49, Felix Cheung wrote:
> I think there are rooms to optimize much more - feel free to propose or contribute!
>
>
>
>
>
>
> On Tue, Mar 8, 2016 at 10:29 AM -0800, "Eric Charles" <er...@apache.org> wrote:
>
>
>
>
>
> Makes sense. No need to run tests if a module fails on compilation,
> format...
>
> On 08/03/16 18:52, Felix Cheung wrote:
>> Right now Travis does a full build first and then run the tests in a separate steps.
>>
>>
>>
>>
>>
>>
>> On Tue, Mar 8, 2016 at 2:36 AM -0800, "Eric Charles" <er...@apache.org> wrote:
>>
>>
>>
>>
>>
>> Hi there,
>>
>> I see tests are disabled on Travis.
>>
>> e.g. From
>> https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt
>>
>> $ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
>> $ export BUILD_FLAG="package -DskipTests"
>>
>> Is this on purpose?
>>
>

Re: Travis Build flags for tests

Posted by Eric Charles <er...@apache.org>.

What are you thinking to: Build time, stability....?

I have seen work to optimize the download of spark.

Travis starts from a clean env which is good but things take time to be 
downloaded and setup.

I guess we have to log each failure which should not occur and tackle 
them. I have seen multiple times such errors which should not occur:

Failed tests: 
ZeppelinSparkClusterTest.pySparkDepLoaderTest:167->getSparkVersionNumber:220 
expected:<FINISHED> but was:<ERROR> 
ZeppelinSparkClusterTest.pySparkAutoConvertOptionTest:112->getSparkVersionNumber:220 
expected:<FINISHED> but was:<ERROR>
   ZeppelinSparkClusterTest.basicRDDTransformationAndActionTest:81 
expected:<FINISHED> but was:<ERROR>
   ZeppelinSparkClusterTest.pySparkTest:90->getSparkVersionNumber:220 
expected:<FINISHED> but was:<ERROR>
   ZeppelinSparkClusterTest.zRunTest:152 expected:<FINISHED> but was:<ERROR>


(https://s3.amazonaws.com/archive.travis-ci.org/jobs/111732702/log.txt)

Apparently checkIfServerIsRunning is the cause - maybe the server takes 
time to open the socket...


On 08/03/16 19:49, Felix Cheung wrote:
> I think there are rooms to optimize much more - feel free to propose or contribute!
>
>
>
>
>
>
> On Tue, Mar 8, 2016 at 10:29 AM -0800, "Eric Charles" <er...@apache.org> wrote:
>
>
>
>
>
> Makes sense. No need to run tests if a module fails on compilation,
> format...
>
> On 08/03/16 18:52, Felix Cheung wrote:
>> Right now Travis does a full build first and then run the tests in a separate steps.
>>
>>
>>
>>
>>
>>
>> On Tue, Mar 8, 2016 at 2:36 AM -0800, "Eric Charles" <er...@apache.org> wrote:
>>
>>
>>
>>
>>
>> Hi there,
>>
>> I see tests are disabled on Travis.
>>
>> e.g. From
>> https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt
>>
>> $ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
>> $ export BUILD_FLAG="package -DskipTests"
>>
>> Is this on purpose?
>>
>

Re: Travis Build flags for tests

Posted by Felix Cheung <fe...@hotmail.com>.

I think there are rooms to optimize much more - feel free to propose or contribute!






On Tue, Mar 8, 2016 at 10:29 AM -0800, "Eric Charles" <er...@apache.org> wrote:





Makes sense. No need to run tests if a module fails on compilation,
format...

On 08/03/16 18:52, Felix Cheung wrote:
> Right now Travis does a full build first and then run the tests in a separate steps.
>
>
>
>
>
>
> On Tue, Mar 8, 2016 at 2:36 AM -0800, "Eric Charles" <er...@apache.org> wrote:
>
>
>
>
>
> Hi there,
>
> I see tests are disabled on Travis.
>
> e.g. From
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt
>
> $ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
> $ export BUILD_FLAG="package -DskipTests"
>
> Is this on purpose?
>

Re: Travis Build flags for tests

Posted by Eric Charles <er...@apache.org>.

Makes sense. No need to run tests if a module fails on compilation, 
format...

On 08/03/16 18:52, Felix Cheung wrote:
> Right now Travis does a full build first and then run the tests in a separate steps.
>
>
>
>
>
>
> On Tue, Mar 8, 2016 at 2:36 AM -0800, "Eric Charles" <er...@apache.org> wrote:
>
>
>
>
>
> Hi there,
>
> I see tests are disabled on Travis.
>
> e.g. From
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt
>
> $ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
> $ export BUILD_FLAG="package -DskipTests"
>
> Is this on purpose?
>

Re: Travis Build flags for tests

Posted by Felix Cheung <fe...@hotmail.com>.

Right now Travis does a full build first and then run the tests in a separate steps.






On Tue, Mar 8, 2016 at 2:36 AM -0800, "Eric Charles" <er...@apache.org> wrote:





Hi there,

I see tests are disabled on Travis.

e.g. From
https://s3.amazonaws.com/archive.travis-ci.org/jobs/114476198/log.txt

$ export PROFILE="-Pspark-1.5 -Phadoop-2.3 -Ppyspark"
$ export BUILD_FLAG="package -DskipTests"

Is this on purpose?