zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Hunt <ph...@apache.org>
Subject Re: ZK Jenkins job updates.
Date Wed, 20 Dec 2017 21:51:33 GMT
I fixed the flakey test reporting job
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-Find-Flaky-Tests/lastSuccessfulBuild/artifact/report.html

As part of this fix I created a specialized branch in the git repo to track
our jenkins tools:
https://github.com/apache/zookeeper/tree/jenkins-tools
if folks have ideas they can submit PRs against this similar to the rest of
the codebase.

Patrick

On Tue, Dec 19, 2017 at 12:03 PM, Patrick Hunt <phunt@apache.org> wrote:

> I've been monitoring and the jobs seem much less flakey, afaict the
> changes have improved things. I recently noticed that our default heap for
> the test vms was just 500mb, I've increased this to 2g for our existing
> jobs and that seems to also be helping.
>
> One side effect of this change is that it broke the "flakey tests report"
> job that Michael added a while back. I'm working on updating the script for
> that to address (we now need to use the logs rather than the console to
> identify failed tests)
>
> Patrick
>
> On Mon, Dec 4, 2017 at 11:31 AM, Abraham Fine <afine@apache.org> wrote:
>
>> Thank you Patrick!
>>
>> This should make debugging flaky tests much less painful.
>>
>> Abe
>>
>> On Sun, Dec 3, 2017, at 17:33, Patrick Hunt wrote:
>> > I made a few updates to the jenkins job configs. Abe pointed out that
>> > while
>> > we are now generating individual logs files for tests (one per junit
>> test
>> > class) we were not capturing them as artifacts of the jenkins jobs. I've
>> > updated the jobs to now capture these files as artifacts which should
>> > simplify debugging.
>> >
>> > We are running with multiple junit test execution threads now (typ. 8 in
>> > 3.5+ version jobs). Having a single "console log" output of the jenkins
>> > job
>> > with all of these test logs inter-mingled is not useful. As such I've
>> > configured test.output=no for the jobs. This simplifies the console
>> > output
>> > and given we have the individual log files now as artifacts it wasn't
>> > very
>> > useful.
>> >
>> > If there are any questions lmk.
>> >
>> > Regards,
>> >
>> > Patrick
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message