Michael, the solaris unit tests seem to be failing pretty consistently with
the same two tests:
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-solaris/1245/#showFailuresLink
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch35_solaris/185/#showFailuresLink
are those two tests captured already, or do we need to create new jiras for
these? (would you mind, thanks!)

Patrick

On Fri, Jul 22, 2016 at 8:51 PM, Patrick Hunt <[email protected]> wrote:

> Thanks for taking this up Michael, much appreciated! If folks are looking
> for ways to participate in the community helping to address these issues is
> a great way to do so, it's also a great way to learn the project!
>
> Patrick
>
> On Fri, Jul 22, 2016 at 2:39 PM, Michael Han <[email protected]> wrote:
>
>> Hi,
>>
>> I've noticed recently that besides the bugs logged as sub-tasks under
>> umbrella ZOOKEEPER-2135
>> <https://issues.apache.org/jira/browse/ZOOKEEPER-2135> (Fix Trunk Build),
>> we are constantly getting pre-commit build failures and nightly build
>> fails
>> caused by other flaky unit tests. Since we mostly rely on unit tests for
>> quality assurance, the existence of flaky tests prevent us from getting a
>> clear picture of quality of the build, and could slow down our
>> dev/review/release process.
>>
>> So as a start step to harden unit tests, I have triaged Apache Jenkins
>> ZooKeeper builds over last two weeks, and created a couple of JIRAs to
>> track the flaky tests got extracted during the triage, and linked those
>> JIRAs under the umbrella ZOOKEEPER-2135. I've started working on some of
>> them. Help is also wanted, from analyzing Jenkins build and log bugs
>> (manually or through a script like this
>> <
>> https://github.com/apache/hadoop/blob/trunk/dev-support/determine-flaky-tests-hadoop.py
>> >),
>> or working on contributing patch that fix the test, or reviewing and (for
>> committers) commit the patch.
>>
>> Let's give these tests more love and make the Jenkins build all green
>> again.
>>
>> --
>> Cheers
>> Michael.
>>
>
>

Reply via email to