Hi,

I got the Jenkins builds for 0.23-PB.  They were cloned from 0.23.  Everything 
looks fine.  Please see the details at the end.

https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-0.23-PB-Build/
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Hdfs-0.23-PB-Build/
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Mapreduce-0.23-PB-Build/

Regards,


Tsz-Wo Nicholas Sze
Hortonworks Inc.
http://hortonworks.com/
---------------------------
Here is more details.  In Common, TestViewFsTrash occasionally fails and it 
also fails on trunk.  Filed HADOOP-8110.  I don't see any failure in HDFS.

For Mapreduce, there were two unit tests, TestNMAuditLogger and 
TestAuditLogger, failed.  TestNMAuditLogger was already fixed in trunk and then 
I merged MAPREDUCE-2942.  TestAuditLogger casued some compilation errors 
earlier in 0.23 since 0.23 did not have PB.  MAPREDUCE-3368 removed the PB 
related code from the TestAuditLogger.  I reverted the changes in 0.23-PB and 
then the test passed.  After fixed the two unit tests, a Jenkins build still 
failed although the maven build inside was success (see below).  I suspect the 
Jenkins configuration has some bugs.  Note that the Jenkins builds for 0.23 
also fail quite frequently.  So the problem is not specific to 0.23-PB.

Below is copied from build #2 of 0.23-PB.
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Mapreduce-0.23-PB-Build/2/console
Note that build #204 of 0.23 has the same failure.
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Mapreduce-0.23-Build/204/console

[INFO] hadoop-mapreduce .................................. SUCCESS [0.077s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 40:46.501s
[INFO] Finished at: Fri Feb 24 13:56:06 UTC 2012
[INFO] Final Memory: 78M/370M
[INFO] ------------------------------------------------------------------------
+ [[ 0 -ne 0 ]]
Build step 'Execute shell' marked build as failure



----- Original Message -----
From: "Tsz Wo (Nicholas), Sze" <[email protected]>
To: "[email protected]" <[email protected]>
Cc: 
Sent: Thursday, February 23, 2012 1:00 PM
Subject: Re: Merging 0.23-PB to 0.23

I ran unit tests when I did the merges.  I will see if I could get a Jenkins 
build on 0.23-PB.


Nicholas



----- Original Message -----
From: Eli Collins <[email protected]>
To: [email protected]; "Tsz Wo (Nicholas), Sze" 
<[email protected]>
Cc: 
Sent: Thursday, February 23, 2012 12:41 PM
Subject: Re: Merging 0.23-PB to 0.23

Thanks Nicholas.

For sanity, Jenkins is clean on this branch? I didn't see a job on
builds.apache.org so assuming you've run it locally.

On Thu, Feb 23, 2012 at 12:31 PM, Tsz Wo (Nicholas), Sze
<[email protected]> wrote:
> Hi Eli,
>
> You indeed did the checking very carefully.  The reason of HDFS-395 is that 
> (1) as you mentioned, it is a significant improvement, and (2) it changes the 
> protocols.  If it is not included, then there will be a lot of code rewrite 
> in 0.23-PB.
>
> Sure, will update the fix version on JIRA.
>
> Thanks.
>
> Nicholas
>
>
> ________________________________
> From: Eli Collins <[email protected]>
> To: [email protected]; "Tsz Wo (Nicholas), Sze" 
> <[email protected]>
> Sent: Wednesday, February 22, 2012 7:41 PM
> Subject: Re: Merging 0.23-PB to 0.23
>
> Hey Nicholas,
>
> Thank you for doing this!   +1 for the merge.
>
> I went through the delta between 0.23-PB and branch-23, and they look
> good.  I noticed some other changes from trunk not-PB related (eg
> HDFS-395) were pulled in, and they were all stuff that were in my
> list:
> http://search-hadoop.com/m/pn6ea1EgPTc1&subj=Re+Merging+some+trunk+changes+to+23
> I'll merge the remainder to branch-23 (primarily the BR scalability
> changes) after you've merged this.
>
> Mind updating jira for the relevant changes to have a 0.23.2 fixVersion?
>
> Thanks,
> Eli
>
> On Wed, Feb 22, 2012 at 12:20 PM, Tsz Wo (Nicholas), Sze
> <[email protected]> wrote:
>> Hi,
>>
>>
>> The IPC protocol buffer feature in trunk is complete.  It is time to merge 
>> 0.23-PB back to 0.23.  Lists of
> 0.23-PB issues which are not in 0.23 can be found in the CHANGES.txt files in 
> the 0.23-PB branch.  I will merge it tomorrow.  Please let me know if you 
> have any concern.
>>
>>
>> Regards,
>>
>> Tsz-Wo Nicholas Sze
>> Hortonworks Inc.
>> http://hortonworks.com/

Reply via email to