Hm, I'm seeing weird flakey tests, tests that typically haven't been
flakey. I also notice test.junit.threads is set to 8 on these jobs,
ala: https://issues.apache.org/jira/browse/ZOOKEEPER-2183

Here's one example
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch35_jdk8/1/

Chris would you be able to take a look? I suspect something in the
test setup with concurrent threads.

Patrick

On Thu, Mar 3, 2016 at 8:48 PM, Patrick Hunt <ph...@apache.org> wrote:
> Also the flakey tests on jenkins are really painful. It's seems like
> it's gotten worse of late and it's more flakey than usual. Just me?
> Notice that we're missing a number of "standard" jobs for branch 3.5,
> I'll try to get the "standard" jobs setup asap.
>
> Patrick
>
> On Thu, Mar 3, 2016 at 4:28 PM, Patrick Hunt <ph...@apache.org> wrote:
>> Looks like Flavio reopened this one, it's another license issue -
>> needs to get into 3.5.2 and trunk:
>>
>> https://issues.apache.org/jira/browse/ZOOKEEPER-2235
>>
>> Patrick
>>
>> On Thu, Mar 3, 2016 at 3:56 PM, Patrick Hunt <ph...@apache.org> wrote:
>>> FYI you can see my ZooKeeper Jira dashboard here: http://bit.ly/1UCURuM
>>>
>>> It's pretty useful to see overall project status as well as the in
>>> progress releases.
>>>
>>> Patrick
>>>
>>> On Thu, Mar 3, 2016 at 3:04 PM, Crowder Tim <timrc...@yahoo.com.invalid> 
>>> wrote:
>>>> Hi Chris-
>>>>
>>>> Any chance of getting ZOOKEEPER-1525 in there?
>>>>
>>>> Thanks!
>>>> .timrc
>>>>
>>>> --------------------------------------------
>>>> On Thu, 3/3/16, Chris Nauroth <cnaur...@hortonworks.com> wrote:
>>>>
>>>>  Subject: 3.5.2-alpha Release Planning
>>>>  To: "dev@zookeeper.apache.org" <dev@zookeeper.apache.org>
>>>>  Date: Thursday, March 3, 2016, 10:12 AM
>>>>
>>>>  This link shows issues currently
>>>>  fixed for 3.5.2:
>>>>
>>>>  https://s.apache.org/n2C6
>>>>
>>>>  This link shows issues still open targeted to 3.5.2:
>>>>
>>>>  https://s.apache.org/nORc
>>>>
>>>>  I had been planning to kick off the release process for a
>>>>  3.5.2-alpha
>>>>  candidate right around now, but after reviewing these lists,
>>>>  I'm inclined
>>>>  to defer it a few more weeks while we work down more
>>>>  blockers.  What do
>>>>  others think?
>>>>
>>>>  On a related note, thank you to Patrick for the recent JIRA
>>>>  clean-up.
>>>>
>>>>  --Chris Nauroth

Reply via email to