On Jul 17, 2015, at 3:07 AM, Steve Loughran wrote:
>
>> On 16 Jul 2015, at 16:05, Allen Wittenauer wrote:
>>
>> “convert this directory of TAP-formatted files to JUnit XML”.
>
> FWIW it's Ant JUnit XML Reporter-formatted XML. Just to make the origins
> clear: it's an ASF format written in, 2
> On 16 Jul 2015, at 16:05, Allen Wittenauer wrote:
>
> “convert this directory of TAP-formatted files to JUnit XML”.
FWIW it's Ant JUnit XML Reporter-formatted XML. Just to make the origins clear:
it's an ASF format written in, 2000 or 2001, probably by sballiez, who also did
the XSL stylesh
On Jul 15, 2015, at 11:22 PM, Bruno P. Kinoshita
wrote:
>
> Good points. This layer between Jenkins and the unit tests seems useful.
Thanks!
We think so too! It’s why we’re working on pulling the code out of
Hadoop to make it more generalized for lots of different projects.
to integrate it with Jenkins.
Cheers
Bruno
[1] http://taint.org/2008/03/26/124602a.html
From: Allen Wittenauer
To: common-dev@hadoop.apache.org; Bruno P. Kinoshita
Sent: Wednesday, July 15, 2015 4:43 AM
Subject: Re: [Test-Patch TLP] consensus on naming
On Jul 14, 2015, at 3
On Jul 14, 2015, at 3:08 AM, Bruno P. Kinoshita
wrote:
> Hi
> Has anyone considered using TAP (Test Anything Protocol) for test reporting?
> [1][2]
> disclaimer: I'm the maintainer of the Jenkins TAP plug-in and tap4j Java
> library
Just to be clear: yetus is about the layer betwee
m/package/yamlish
[6] https://github.com/TestAnything/Specification/issues/11
[7] https://wiki.jenkins-ci.org/display/JENKINS/TAP+Plugin
[8] http://tap4j.org/[9] https://issues.jenkins-ci.org/browse/JENKINS-19154
From: Steve Loughran
To: "common-dev@hadoop.apache.org"
Sent: Monday, J
On Jul 13, 2015, at 2:52 AM, Steve Loughran wrote:
>
> nothing particular, except I want to do something better with test running
> and reporting
...
> ultimately I'd like to be able to stream test events from test runners & log
> events from (distributed) processes together for a linearize
> On 12 Jul 2015, at 22:32, Sean Busbey wrote:
>
> sure. what did you have in mind?
>
> Last time it was discussed we were going to wait to overhaul the repo until
> we have a new repo to move to.
>
> On Sat, Jul 11, 2015 at 7:40 AM, Steve Loughran
> wrote:
>
>> +1,
>>
>> could you structur
sure. what did you have in mind?
Last time it was discussed we were going to wait to overhaul the repo until
we have a new repo to move to.
On Sat, Jul 11, 2015 at 7:40 AM, Steve Loughran
wrote:
> +1,
>
> could you structure the source tree/build so that adding new modules is
> easy?
>
>
> > On
+1,
could you structure the source tree/build so that adding new modules is easy?
> On 10 Jul 2015, at 06:08, Kengo Seki wrote:
>
> +1 for Yetus. Simple and distinctive.
>
> On Friday, July 10, 2015, Kengo Seki wrote:
>
>>
>>
>> On Wednesday, July 8, 2015, Tsuyoshi Ozawa > > wrote:
>>
>
+1 for Yetus. Simple and distinctive.
On Friday, July 10, 2015, Kengo Seki wrote:
>
>
> On Wednesday, July 8, 2015, Tsuyoshi Ozawa > wrote:
>
>> Hi Sean,
>>
>> +1 for Yetus since it sounds good name to me.
>>
>> Thanks
>> - Tsuyoshi
>>
>> On Wed, Jul 8, 2015 at 2:42 PM, Sean Busbey wrote:
>> >
On Wednesday, July 8, 2015, Tsuyoshi Ozawa wrote:
> Hi Sean,
>
> +1 for Yetus since it sounds good name to me.
>
> Thanks
> - Tsuyoshi
>
> On Wed, Jul 8, 2015 at 2:42 PM, Sean Busbey > wrote:
> > Hi folks!
> >
> > It's almost time for the July board meeting, so we need to get the ball
> > rollin
Hi Sean,
+1 for Yetus since it sounds good name to me.
Thanks
- Tsuyoshi
On Wed, Jul 8, 2015 at 2:42 PM, Sean Busbey wrote:
> Hi folks!
>
> It's almost time for the July board meeting, so we need to get the ball
> rolling on the proposal for a new TLP focused on QA[1].
>
> Once issue outstandin
Hi folks!
It's almost time for the July board meeting, so we need to get the ball
rolling on the proposal for a new TLP focused on QA[1].
Once issue outstanding from the original discussion is consensus on a name.
We need to get some consensus together so that I can start verifying that
the name
14 matches
Mail list logo
