I believe this is not a regression -- I've seen some tests failed
miserably because the build artifacts are destroyed during the
execution of the unit tests.
~Haohui
On Wed, Apr 22, 2015 at 12:10 AM, Allen Wittenauer wrote:
>
> Some status:
>
> * So far, HADOOP-11627 was filed which is luckily a
On Wed, Apr 22, 2015 at 2:10 AM, Allen Wittenauer wrote:
>
>
> * There have been a few runs which seems to indicate that *something* is
> destroying the artifact directory in the middle of runs…. which is very
> very odd and something I hadn’t seen in any of my testing. In any case, I
> clearly
Err, first jira mentioned should be HADOOP-11861.
On Apr 22, 2015, at 8:10 AM, Allen Wittenauer wrote:
>
> Some status:
>
> * So far, HADOOP-11627 was filed which is luckily an extremely easy bug to
> fix.
>
> * There have been a few runs which seems to indicate that *something* is
> destr
Some status:
* So far, HADOOP-11627 was filed which is luckily an extremely easy bug to fix.
* There have been a few runs which seems to indicate that *something* is
destroying the artifact directory in the middle of runs…. which is very very
odd and something I hadn’t seen in any of my testi
FYI, MAPREDUCE-6324 is the first JIRA to be tested with the new code in place
if someone hasn’t seen the new output.
On Apr 21, 2015, at 9:06 PM, Allen Wittenauer wrote:
>
>
> Just a heads up that I’ll be committing this to trunk and branch-2 here
> in a bit. I’ll watch it over the n
Just a heads up that I’ll be committing this to trunk and branch-2 here
in a bit. I’ll watch it over the next hour or two before heading off to bed.
(I’m in London at the moment.) If there are any issues, revert and drop a note
in HADOOP-11746 with any issues.
Despite what will hope
I'd like to thank Allen Wittenauer for his work on HADOOP-11746 to rewrite
test-patch.sh. There is a lot of nice new functionality in there. My
favorite part is that some patches will execute much faster, so I expect
this will make the project more efficient overall at moving patches
through the
