The failure is due to a build ordering issue, not a product or test bug. Let’s pull in the fix and respin. If you do see an issue please speak up ASAP so we get this release out.
Thanks,
Anthony
> On Jul 28, 2016, at 2:58 PM, Darrel Schneider <dschnei...@pivotal.io> wrote:
>
> flaky tests are supposed to be flickering. In this case it seems like it
> fails everytime
>
>
> On Thu, Jul 28, 2016 at 1:38 PM, Bruce Schuchardt <bschucha...@pivotal.io>
> wrote:
>
>> commit 4c5a699490b2702d6abe3a40e5d74a7e2f6b5acf
>> Author: Bruce Schuchardt <bschucha...@pivotal.io>
>> Date: Tue Jul 26 13:49:00 2016 -0700
>>
>> fixes flakyTest target to allow it to run Rest API tests
>>
>> diff --git a/geode-assembly/build.gradle b/geode-assembly/build.gradle
>> index fdd6e25..499eca2 100755
>> --- a/geode-assembly/build.gradle
>> +++ b/geode-assembly/build.gradle
>> @@ -387,6 +387,7 @@ def dependOnInstalledProduct = {
>> test dependOnInstalledProduct
>> distributedTest dependOnInstalledProduct
>> integrationTest dependOnInstalledProduct
>> +flakyTest dependOnInstalledProduct
>>
>> // Make build final task to generate all test and product resources
>> build.dependsOn installDist
>>
>>
>>
>> Le 7/28/2016 à 1:22 PM, William Markito a écrit :
>>
>>> My assumption here was that flaky would not be preventing the release, but
>>> indeed it's worth double checking, specially if there is something we
>>> could
>>> do in the build pipeline to fix it...
>>>
>>> On Thu, Jul 28, 2016 at 12:02 PM, Dan Smith <dsm...@pivotal.io> wrote:
>>>
>>> Bruce pointed out that there is a consistently failing test on this
>>>> release
>>>> branch. I'm not sure if this should hold things up or not since this is
>>>> marked as a "flaky" test.
>>>>
>>>> :*geode-assembly:flakyTest*
>>>>
>>>>
>>>>
>>>> com.gemstone.gemfire.rest.internal.web.controllers.RestAPIsOnMembersFunctionExecutionDUnitTest
>>>>
>>>>> testFunctionExecutionOnAllMembers FAILED
>>>>>
>>>> java.lang.AssertionError: unable to locate geode-web-api WAR file
>>>>
>>>> java.lang.NullPointerException
>>>>
>>>>
>>>>
>>>> On Wed, Jul 27, 2016 at 12:28 PM, William Markito <wmark...@pivotal.io>
>>>> wrote:
>>>>
>>>> All,
>>>>>
>>>>> This is the sixth release candidate Apache Geode, version
>>>>> 1.0.0-incubating.M3.
>>>>>
>>>>> We're including the feedback received in RC5 fixing a classpath issue on
>>>>> 'gfsh' caused by wrong build arguments.
>>>>>
>>>>> Thanks to all the community members to drive towards this milestone!
>>>>>
>>>>> It fixes the following issues:
>>>>>
>>>>>
>>>>>
>>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420&version=12335358
>>>>
>>>>> *** Please download, test and vote by Monday, August 1, 0800 hrs US
>>>>> Pacific.
>>>>>
>>>>> Note that we are voting upon the source (tag):
>>>>> rel/v1.0.0-incubating.M3.RC6
>>>>>
>>>>>
>>>>>
>>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M3.RC6
>>>>
>>>>> Commit ID: c70efdff8fda585d5e0aa6ab0229cac6f1757d59
>>>>>
>>>>>
>>>>>
>>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=commit;h=c70efdff8fda585d5e0aa6ab0229cac6f1757d59
>>>>
>>>>> Source and binary files:
>>>>>
>>>>>
>>>>>
>>>> https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M3.RC6/
>>>>
>>>>> For this release the documentation on how to install and use Apache
>>>>> Geode
>>>>> are hosted
>>>>> on pivotal.io:
>>>>> http://geode.docs.pivotal.io
>>>>>
>>>>> Maven staging repo:
>>>>> https://repository.apache.org/content/repositories/orgapachegeode-1010
>>>>>
>>>>> Geode's KEYS file containing PGP keys we use to sign the release:
>>>>>
>>>>>
>>>>>
>>>>>
>>>> https://github.com/apache/incubator-geode/blob/release/1.0.0-incubating.M3/KEYS
>>>>
>>>>> Release Key: pub 4096R/7AAED8BB 2016-07-13
>>>>> Fingerprint: 8E06 B711 DB13 3AE7 0CC1 ABDE 6A14 F0BC 7AAE D8BB
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --
>>>>> ~/William
>>>>>
>>>>>
>>>
>>>
>>
signature.asc
Description: Message signed with OpenPGP using GPGMail
