Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Subject: Re: [Test-Patch TLP] consensus on naming
MIME-Version: 1.0
From: Steve Loughran <stevel@hortonworks.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Thread-Topic: [Test-Patch TLP] consensus on naming
Thread-Index: 
 AQHQuUEQXaw+HiV2H0S+Q66IViYCW53Ro/kAgAL7OACAAACAAIACEPwAgAImmQCAAM8MgA==
Date: Mon, 13 Jul 2015 09:52:40 +0000
Message-ID: <0C6A1A6C-8EB0-47EB-91B9-EED41FCBFC3F@hortonworks.com>
References: 
 <CAGHyZ6L0WVvnvKqwSTPNKdiWjwsn03=u_vcTWAppCKiJhdA8FQ@mail.gmail.com>
 <CAAD07OJETT0X_rXpDNhqBcmBncbo7zeeq6DB-P1hrZgPL1Vw4Q@mail.gmail.com>
 <CAEhbgSKaZd1soTch_2vc5dn+0FKFaKku7hp8zCgj2Cun2hs6+A@mail.gmail.com>
 <CAEhbgSJ-FeQAMasu9JRHnvUDjn0Yga5jr2UUNEmbEufVQ8CO-g@mail.gmail.com>
 <02959AF3-E8D3-409C-8555-E5DD1718C1C2@hortonworks.com>
 <CAGHyZ6KzLV-Pii=KCdtK0knVwfAKA3Po-2rOeUG3JgFQVEqNPA@mail.gmail.com>
In-Reply-To: 
 <CAGHyZ6KzLV-Pii=KCdtK0knVwfAKA3Po-2rOeUG3JgFQVEqNPA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4AA0C868E48E0146A4CF729F1F177BB2@exch080.serverpod.net>
Content-Transfer-Encoding: quoted-printable


> On 12 Jul 2015, at 22:32, Sean Busbey <busbey@cloudera.com> wrote:
>=20
> sure. what did you have in mind?
>=20
> Last time it was discussed we were going to wait to overhaul the repo unt=
il
> we have a new repo to move to.
>=20
> On Sat, Jul 11, 2015 at 7:40 AM, Steve Loughran <stevel@hortonworks.com>
> wrote:
>=20
>> +1,
>>=20
>> could you structure the source tree/build so that adding new modules is
>> easy?


nothing particular, except I want to do something better with test running =
and reporting

http://steveloughran.blogspot.co.uk/2015/05/distributed-system-testing-wher=
e-now.html
http://steveloughran.blogspot.co.uk/2015/06/why-is-so-much-of-my-life-waste=
d.html

I actually think that Yetus may be the wrong place; I want to do some baby =
steps with

-something to import ant Junit XML and generate some aggregate (avro?) form=
at
-spark libs for analysis in ipython, zepplin of test runs and test runs acr=
oss time and configurations.

ultimately I'd like to  be able to stream test events from test runners & l=
og events from (distributed) processes together for a linearized event log =
which could go into better analysis & some webapp to view better, with some=
 as-test-run reporting.

I think overall this wouldn't fit into Yetus, something way downstream -but=
 I might like some of the test & log reporting in there if that helps get t=
he dependency graph right.

Like I said: want. Spare time work, which is why I didn't propose a talk on=
 it at apachecon EU data.