Re: Build failed in Jenkins: Geode-nightly #1240

[Anthony Baker]

I added a build step to clean the workspace.

Anthony


> On Jun 28, 2018, at 10:24 PM, Apache Jenkins Server 
>  wrote:
> 
> 
> * What went wrong:
> Execution failed for task ':rat'.
>> Found 1 files with unapproved/unknown licenses. See 
>> 

Build failed in Jenkins: Geode-nightly #1241

[Apache Jenkins Server]

See 

--
[...truncated 112.86 KB...]
> Task :geode-connectors:spotlessCheck
> Task :geode-connectors:test
> Task :geode-core:assemble
> Task :geode-core:checkMissedTests
> Task :geode-core:spotlessJava
> Task :geode-core:spotlessJavaCheck
> Task :geode-core:spotlessCheck
> Task :geode-core:test
> Task :geode-cq:assemble

> Task :geode-cq:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-cq:processTestResources
> Task :geode-cq:testClasses
> Task :geode-cq:checkMissedTests
> Task :geode-cq:spotlessJava
> Task :geode-cq:spotlessJavaCheck
> Task :geode-cq:spotlessCheck
> Task :geode-cq:test
> Task :geode-experimental-driver:jar
> Task :geode-experimental-driver:javadoc
> Task :geode-experimental-driver:javadocJar
> Task :geode-experimental-driver:sourcesJar
> Task :geode-experimental-driver:signArchives SKIPPED
> Task :geode-experimental-driver:assemble

> Task :geode-experimental-driver:compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-experimental-driver:processTestResources
> Task :geode-experimental-driver:testClasses
> Task :geode-experimental-driver:checkMissedTests
> Task :geode-experimental-driver:spotlessJava
> Task :geode-experimental-driver:spotlessJavaCheck
> Task :geode-experimental-driver:spotlessCheck
> Task :geode-experimental-driver:test
> Task :geode-json:assemble
> Task :geode-json:compileTestJava NO-SOURCE
> Task :geode-json:processTestResources
> Task :geode-json:testClasses
> Task :geode-json:checkMissedTests NO-SOURCE
> Task :geode-json:spotlessJava
> Task :geode-json:spotlessJavaCheck
> Task :geode-json:spotlessCheck
> Task :geode-json:test NO-SOURCE
> Task :geode-old-versions:javadoc NO-SOURCE
> Task :geode-junit:javadoc
> Task :geode-junit:javadocJar
> Task :geode-junit:sourcesJar
> Task :geode-junit:signArchives SKIPPED
> Task :geode-junit:assemble

> Task :geode-junit:compileTestJava
Note: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: 

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-junit:processTestResources
> Task :geode-junit:testClasses
> Task :geode-junit:checkMissedTests
> Task :geode-junit:spotlessJava
> Task :geode-junit:spotlessJavaCheck
> Task :geode-junit:spotlessCheck
> Task :geode-junit:test
> Task :geode-lucene:assemble

> Task :geode-lucene:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-lucene:processTestResources
> Task :geode-lucene:testClasses
> Task :geode-lucene:checkMissedTests
> Task :geode-lucene:spotlessJava
> Task :geode-lucene:spotlessJavaCheck
> Task :geode-lucene:spotlessCheck
> Task :geode-lucene:test
> Task :geode-old-client-support:assemble
> Task :geode-old-client-support:compileTestJava
> Task :geode-old-client-support:processTestResources NO-SOURCE
> Task :geode-old-client-support:testClasses
> Task :geode-old-client-support:checkMissedTests
> Task :geode-old-client-support:spotlessJava
> Task :geode-old-client-support:spotlessJavaCheck
> Task :geode-old-client-support:spotlessCheck
> Task :geode-old-client-support:test
> Task :geode-old-versions:javadocJar
> Task :geode-old-versions:sourcesJar
> Task :geode-old-versions:signArchives SKIPPED
> Task :geode-old-versions:assemble
> Task :geode-old-versions:compileTestJava NO-SOURCE
> Task :geode-old-versions:processTestResources NO-SOURCE
> Task :geode-old-versions:testClasses UP-TO-DATE
> Task :geode-old-versions:checkMissedTests NO-SOURCE
> Task :geode-old-versions:spotlessJava
> Task :geode-old-versions:spotlessJavaCheck
> Task :geode-old-versions:spotlessCheck
> Task :geode-old-versions:test NO-SOURCE
> Task :geode-protobuf:assemble
Download 
https://repo.maven.apache.org/maven2/org/powermock/powermock-api-mockito/1.7.1/powermock-api-mockito-1.7.1.pom
Download 
https://repo.maven.apache.org/maven2/org/powermock/powermock-api-mockito/1.7.1/powermock-api-mockito-1.7.1.jar

> Task :geode-protobuf:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-protob

Re: DISCUSS: Refactor test source set for integrationTest and distributedTest

[Jacob Barrett]

Opened a ticket here https://issues.apache.org/jira/browse/GEODE-5363


On Thu, Jun 28, 2018 at 10:36 AM Galen O'Sullivan 
wrote:

> +1 to the new test organization.
>
> And I agree with Patrick's explanation of which is the more stable test
> category.
>
> On Thu, Jun 28, 2018 at 9:47 AM, Patrick Rhomberg 
> wrote:
>
> > @Dale
> >   It seems to me that the Unit / Distributed / etc would be the more
> stable
> > purpose, and as importantly, each level is mutually-exclusive with any
> > other.
> >   At least under our current categorization tags, the functional area
> > categories don't form a partition on our test set.  For instance, the
> > GatewayLegacyAuthenticationRegressionTest is both a WanTest and a
> > SecurityTest.
> >
> > On Wed, Jun 27, 2018 at 10:19 AM, Kirk Lund  wrote:
> >
> > > Don't forget to add "acceptanceTest/"
> > >
> > > On Tue, Jun 26, 2018 at 3:36 PM, Jacob Barrett 
> > > wrote:
> > >
> > > > I'd like to suggest that we refactor our current test source set,
> which
> > > > contains both unit, integration and distributed tests, into distinct
> > > source
> > > > sets, test, integrationTest, distributedTest. These source sets would
> > > > replace the use of the primary categories UnitTest, IntegrationTest
> and
> > > > DistributedTest.
> > > >
> > > > The catalyst for this change is an issue that Gradle's test runner
> > > doesn't
> > > > pre-filter categories when launching tests, so if the tests are
> > launched
> > > in
> > > > separate JVMs or Docker containers, like :distributeTest task, the
> cost
> > > of
> > > > spinning up those resources is realized only to immediately exit
> > without
> > > > running any test for all test classes in the module. Switching to
> > > separate
> > > > source sets for each category would remove the need to filter on
> > category
> > > > and only tests in the corresponding source set would get executed in
> > > their
> > > > external JVM or Docker container. An example of this issue is
> > > > geode-junit:distributedTest task, which forks all test classes in
> > > separate
> > > > JVMs but never actually runs any tests since there are no
> > DistributedTest
> > > > tagged tests.
> > > >
> > > > The secondary effect is a way too isolate dependencies in each of the
> > > > source sets. Unit tests in the test set would not have dependencies
> > need
> > > > for integration tests or distributed test so that if you accidentally
> > > tried
> > > > to import classes from those frameworks you would get a compiler
> > failure.
> > > > Likewise, integration tests would not include distributed test
> > framework
> > > > dependencies. Any shared test classes like mock, dummies, fakes, etc.
> > > could
> > > > be shared in a commonTest source set, but would not contain any tests
> > > > itself.
> > > >
> > > > The proposed structure would look like this:
> > > >
> > > > test/ - only contains unit tests.
> > > > integrationTest/ - only contains integration style tests.
> > > > distributedTest/ - only includes DUnit based tests.
> > > > commonTest/ - includes commonly shared classes between each test
> > > category.
> > > > Does not contain any classes.
> > > >
> > > > Thoughts?
> > > >
> > > > -Jake
> > > >
> > >
> >
>

Geode unit tests completed in 'develop/UITests' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/123

Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/113

Geode unit tests completed in 'develop/UITests' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/124

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #963 was SUCCESSFUL (with 2423 tests)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #963 was successful.
---
Scheduled
2425 tests in total.

https://build.spring.io/browse/SGF-NAG-963/





--
This message is automatically generated by Atlassian Bamboo

Geode unit tests 'develop/DistributedTest' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/88