OK, first report was sent out in lieu of the map reduce and common
reports. I'll turn off HDFS and YARN next week some time. For the comparable
OS X report, I need:
* YARN-5121 rebased and committed
* a fix for YETUS-414 (which I'm testing)
* and potentially ne
I think the new formatting makes it a lot easier to pick out a specific
log file link. Thank you for making that change.
--Chris Nauroth
On 6/3/16, 7:53 AM, "Allen Wittenauer"
wrote:
>
>Thanks all. As soon as YETUS-390 gets committed, I'll start publishing
>the reports to *-dev.
>
>FWIW, h
Thanks all. As soon as YETUS-390 gets committed, I'll start publishing the
reports to *-dev.
FWIW, here's last night's. It makes it easy to find out now when committers
are opening ignoring findbugs warnings. (The latest from YARN-5180. It
started showing up yesterday.)
For more details
+1 from me too.
-Akira
On 6/3/16 01:41, Sangjin Lee wrote:
Sounds good. +1.
On Thu, Jun 2, 2016 at 3:28 AM Steve Loughran
wrote:
On 1 Jun 2016, at 04:53, Andrew Wang wrote:
I'm in favor of something that helps unify the current mess of Jenkins
jobs. We do something similar for our intern
Sounds good. +1.
On Thu, Jun 2, 2016 at 3:28 AM Steve Loughran
wrote:
>
> > On 1 Jun 2016, at 04:53, Andrew Wang wrote:
> >
> > I'm in favor of something that helps unify the current mess of Jenkins
> > jobs. We do something similar for our internal Hadoop repo: each branch
> has
> > a "build.sh
> On 1 Jun 2016, at 04:53, Andrew Wang wrote:
>
> I'm in favor of something that helps unify the current mess of Jenkins
> jobs. We do something similar for our internal Hadoop repo: each branch has
> a "build.sh" and "test.sh" script that builds and then runs the tests. This
> predates Yetus, e
Thanks again, Allen.
Just to make sure it's clear, I consider all of my feedback quite minor.
If something big can't get done right away, like changing "patch" in the
file names, then I wouldn't want it to block proceeding with rearranging
our Jenkins jobs.
--Chris Nauroth
On 6/1/16, 11:18 AM
> On Jun 1, 2016, at 10:51 AM, Chris Nauroth wrote:
> It looks like Failed junit tests removes the "org.apache" prefix, but
> Timed out junit tests does not. If possible, it would be nice for this to
> be consistent.
Ha. It's been that way in Yetus for a very, very long time. I've
ope
Hi Allen,
+1 overall for the proposal. Thank you for doing this.
A few minor notes on the content of the report:
It looks like Failed junit tests removes the "org.apache" prefix, but
Timed out junit tests does not. If possible, it would be nice for this to
be consistent.
The naming of log fil
> On May 31, 2016, at 8:53 PM, Andrew Wang wrote:
>
> I'm in favor of something that helps unify the current mess of Jenkins
> jobs. We do something similar for our internal Hadoop repo: each branch has
> a "build.sh" and "test.sh" script that builds and then runs the tests. This
> predates Yetu
I'm in favor of something that helps unify the current mess of Jenkins
jobs. We do something similar for our internal Hadoop repo: each branch has
a "build.sh" and "test.sh" script that builds and then runs the tests. This
predates Yetus, else we'd probably have used that. So +1 from me.
One thing
Hey gang.
I’ve been thinking a lot over the past few months about the various
Jenkins jobs that we have that run after a commit. Their job is to tell us
when a commit break a unit test. They eat up an incredible amount of time on
the build infrastructure and I’m not really sure if the
12 matches
Mail list logo
