Hi Matthieu,

That's a known flaky test on functionality that we think no one uses (and 
probably should be deprecated/removed). It's safe to ignore.

Thanks,
Kanak

> Subject: Re: [VOTE] Apache Helix 0.6.3 Release
> From: [email protected]
> Date: Wed, 19 Mar 2014 10:22:54 +0100
> To: [email protected]
> 
> Hi,
> 
> I downloaded the source version, tried to run the build with the test suite, 
> but it failed. Then I found that TestSimpleWildcardAlert is failing 
> intermittently. Reproduced on mac and linux.
> 
> To reproduce, just run that test a few times ( mvn test 
> -Dtest=TestSimpleWildcardAlert )
> 
> Not sure about how to interpret that failure though, and whether it is a 
> symptom of an important issue or not.
> 
> Matthieu
> 
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.helix.healthcheck.TestSimpleWildcardAlert
> Configuring TestNG with: TestNGMapConfigurator
> Start zookeeper at localhost:2183 in thread main
> START testSimpleWildcardAlert at Wed Mar 19 10:13:55 CET 2014
> true: 
> ClusterStateVerifier$BestPossAndExtViewZkVerifier(TestSimpleWildcardAlert@localhost:2183):
>  wait 1141ms to verify
> alert bean (localhost_12947.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12945.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12948.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12944.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12946.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean AlertSummary_TestSimpleWildcardAlert exposed to jmx
> alert bean (localhost_12947.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12945.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12948.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12944.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean (localhost_12946.RestQueryStats@DBName#TestDB0.latency)GREATER(10) 
> exposed to jmx
> alert bean AlertSummary_TestSimpleWildcardAlert exposed to jmx
> alert bean (localhost_12947.RestQueryStats@DBName#TestDB0.latency)GREATER(15) 
> exposed to jmx
> alert bean (localhost_12945.RestQueryStats@DBName#TestDB0.latency)GREATER(15) 
> exposed to jmx
> alert bean (localhost_12948.RestQueryStats@DBName#TestDB0.latency)GREATER(15) 
> exposed to jmx
> alert bean (localhost_12944.RestQueryStats@DBName#TestDB0.latency)GREATER(15) 
> exposed to jmx
> alert bean (localhost_12946.RestQueryStats@DBName#TestDB0.latency)GREATER(15) 
> exposed to jmx
> alert bean AlertSummary_TestSimpleWildcardAlert exposed to jmx
> Shut down zookeeper at port 2183 in thread main
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.979 sec 
> <<< FAILURE!
> testSimpleWildcardAlert(org.apache.helix.healthcheck.TestSimpleWildcardAlert) 
>  Time elapsed: 5.389 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<true> but was:<false>
>       at org.testng.Assert.fail(Assert.java:89)
>       at org.testng.Assert.failNotEquals(Assert.java:480)
>       at org.testng.Assert.assertTrue(Assert.java:37)
>       at org.testng.Assert.assertTrue(Assert.java:47)
>       at 
> org.apache.helix.healthcheck.TestSimpleWildcardAlert.testSimpleWildcardAlert(TestSimpleWildcardAlert.java:232)
> 
> 
> Results :
> 
> Failed tests:
>   TestSimpleWildcardAlert.testSimpleWildcardAlert:232 expected:<true> but 
> was:<false>
> 
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> 
> 
> 
> On Mar 17, 2014, at 21:13 , Kanak Biscuitwala <[email protected]> wrote:
> 
> > Hi,
> > 
> > This is to call for a vote on releasing the following candidate as Apache 
> > Helix 0.6.3. This is the first release candidate of this particular 
> > release, which is the fourth release of Helix 0.6.x, as well as the first 
> > release of Helix as a top-level Apache project.
> > 
> > Apache Helix is a generic cluster management framework that makes it easy 
> > to build partitioned and replicated, fault-tolerant and scalable 
> > distributed systems.
> > 
> > Release notes:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314020&version=12326504
> > 
> > Release artifacts:
> > https://repository.apache.org/content/repositories/orgapachehelix-1000
> > 
> > Distribution:
> > * binaries:
> > https://dist.apache.org/repos/dist/dev/helix/0.6.3/binaries/
> > * sources:
> > https://dist.apache.org/repos/dist/dev/helix/0.6.3/src/
> > 
> > The 0.6.3 release tag:
> > https://git-wip-us.apache.org/repos/asf?p=helix.git;a=tag;h=refs/tags/helix-0.6.3
> > 
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/helix/KEYS
> > 
> > Please vote on the release. The vote will be open for 72 hours.
> > 
> > [+1] -- "YES, release"
> > [0] -- "No opinion"
> > [-1] -- "NO, do not release"
> > 
> > Thanks,
> > The Apache Helix Team                                         
> 
                                          

Reply via email to