can you see if hudson is working on common-dev first?
confirmed.
nige
On Feb 8, 2011, at 3:21 PM, Ian Holsman wrote:
I'll check it out later on today.
even if it is sending from the wrong email address, I should be able to
moderate them through regardless. (I haven't seen any recently)
Hmm, haven't seen Hudson post build failures to the common-dev list lately.
Ian, can you check that hud...@hudson.apache.org is still subscribed to
common-dev@. If not, please add it.
Thx,
Nige
On Feb 1, 2011, at 11:27 AM, Giridharan Kesavan wrote:
Konstantin,
trunk/artifacts gets
Hi Nige.
I've subscribed it now. as it's wasn't on the subscriber list. we do have
hud...@lucene.zones.apache.org.
but I haven't seen any moderation notices for it either... so I'm not sure it
is generating emails.
On Feb 9, 2011, at 3:32 AM, Nigel Daley wrote:
Hmm, haven't seen Hudson post
ah, that's the old address. I wonder how many of our lists have the old one...
nige
On Feb 8, 2011, at 11:31 AM, Ian Holsman wrote:
Hi Nige.
I've subscribed it now. as it's wasn't on the subscriber list. we do have
hud...@lucene.zones.apache.org.
but I haven't seen any moderation
Giri,
Looking at configuration of Hadoop-Common-trunk-Commit/
There seems to be errors in the Post-build Actions.
It is complaining that
'trunk' exists but not 'trunk/artifacts/...'
Is it possible that this misconfiguration is the reason of failures?
--Konstantin
On Mon, Jan 31, 2011 at 4:40
Konstantin,
trunk/artifacts gets populated when the jar and the tar ant target are
successful.
The main reason for the build failure so far is the build abort time
configuration. It was set to 30mins.
I have increased the build abort time and the builds are going on fine
Giri,
Thanks a lot for fixing this.
I see it is working now.
--Konstantin
On Tue, Feb 1, 2011 at 11:27 AM, Giridharan Kesavan
gkesa...@yahoo-inc.comwrote:
Konstantin,
trunk/artifacts gets populated when the jar and the tar ant target are
successful.
The main reason for the build failure so
Hey Konstantin,
The only build breakage I saw from HADOOP-6904 is MAPREDUCE-2290,
which was fixed. Trees from trunk are compiling against each other
for me (eg each installed to a local maven repo), perhaps the upstream
maven repo hasn't been updated with the latest bits yet.
Thanks,
Eli
On
The has been a problem with more than one build failing (Mahout is the one
that I saw first) due to a change in maven version which meant that the
clover license isn't being found properly. At least, that is the tale I
heard from infra.
On Mon, Jan 31, 2011 at 1:31 PM, Eli Collins
Current trunk for HDFS and MapReduce are not compiling at the moment. Try to
build trunk.
This is the result of that changes to common api introduced by HADOOP-6904
are not promoted to HDFS and MR trunks.
HDFS-1335 and MAPREDUCE-2263 depend on these changes.
Common is not promoted to HDFS and MR
On Mon, Jan 31, 2011 at 1:57 PM, Konstantin Shvachko
shv.had...@gmail.comwrote:
Anybody with gcc active could you please verify if the problem is caused by
HADOOP-6864.
I can build common trunk just fine on CentOS 5.5 including native.
I think the issue is somehow isolated to the build
By manually installing a new core jar into the cache, I can compile
trunk. Looks like we just need to kick a new Core into maven. Are
there instructions somewhere for committers to do this? I know Nigel
and Owen know how, but I don't know if the knowledge is diffused past
them.
-Jakob
On Mon,
ant mvn-deploy would publish snapshot artifact to the apache maven repository
as long you have the right credentials in ~/.m2/settings.xml.
For settings.xml template pls look at http://wiki.apache.org/hadoop/HowToRelease
I'm pushing the latest common artifacts now.
-Giri
On Jan 31, 2011, at
Giri
looks like the last run you started failed the same way as previous ones.
Any thoughts on what's going on?
Thanks,
--Konstantin
On Mon, Jan 31, 2011 at 3:33 PM, Giridharan Kesavan
gkesa...@yahoo-inc.comwrote:
ant mvn-deploy would publish snapshot artifact to the apache maven
repository as
Konstantin,
I think I need to restart the slave which is running the commit build. For now
I have published the common artifact manually from commandline.
Thanks,
Giri
On Jan 31, 2011, at 4:27 PM, Konstantin Shvachko wrote:
Giri
looks like the last run you started failed the same way as
Thanks, Giri.
--Konst
On Mon, Jan 31, 2011 at 4:40 PM, Giridharan Kesavan
gkesa...@yahoo-inc.comwrote:
Konstantin,
I think I need to restart the slave which is running the commit build. For
now I have published the common artifact manually from commandline.
Thanks,
Giri
On Jan 31, 2011,
16 matches
Mail list logo
