Thanks, gentlemen. I've opened and taken responsibility for
https://issues.apache.org/jira/browse/HADOOP-9359. Giri Kesavan has agreed
to help with the parts that require Jenkins admin access.
Thanks,
--Matt
On Mon, Mar 4, 2013 at 5:00 PM, Konstantin Shvachko wrote:
> +1 on the merge.
>
> I
+1 on the merge.
I am glad we agreed.
Having Jira to track the CI effort is a good idea.
Thanks,
--Konstantin
On Mon, Mar 4, 2013 at 3:29 PM, Matt Foley wrote:
> Thanks. I agree Windows -1's in test-patch should not block commits.
>
> --Matt
>
>
>
> On Mon, Mar 4, 2013 at 2:30 PM, Konstantin S
Ok, looks like we are converging on this across a few hundred emails ;)
So, as has been stated elsewhere: test-patch will be improved to fully support
Windows; furthermore -1 from Windows' test-patch won't block Linux commits.
This is ok with me.
Can we have a JIRA ticket for that test-patch work
[
https://issues.apache.org/jira/browse/MAPREDUCE-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla resolved MAPREDUCE-5031.
-
Resolution: Duplicate
Closing as a duplicate of MAPREDUCE-5028 on [~chris.dou
Thanks. I agree Windows -1's in test-patch should not block commits.
--Matt
On Mon, Mar 4, 2013 at 2:30 PM, Konstantin Shvachko wrote:
> On Mon, Mar 4, 2013 at 12:22 PM, Matt Foley
> wrote:
> > Konstantine, you have voted -1, and stated some requirements before
> you'll
> > withdraw that -1.
On Mon, Mar 4, 2013 at 12:22 PM, Matt Foley wrote:
> Konstantine, you have voted -1, and stated some requirements before you'll
> withdraw that -1. As I plan to do work to fulfill those requirements, I
> want to make sure that what I'm proposing will, in fact, satisfy you.
> That's why I'm asking
Konstantine, you have voted -1, and stated some requirements before you'll
withdraw that -1. As I plan to do work to fulfill those requirements, I
want to make sure that what I'm proposing will, in fact, satisfy you.
That's why I'm asking, if we implement full "test-patch" integration for
Windows
There are 3 types of locality.
- data local (node local) - your task gets scheduled on the node where the
data is
- rack local - your task is scheduled on the same rack as the data
(usually 20-40 nodes in a rack), but its not on the exact node with the
data.
- off-switch (off-rack) - your task is
