Sorry about that. Hudson operation seems erratic to me going by its
reports to the list. This morning it ran and completed a patch out of
sequence -- hadoop-1421 -- making me think it had lost all memory of
previous submissions or at least, had dropped my previous submissions
over the last few days. That it ran v2 of the hadoop-1465 rather than
the latest also made me think it had lost its senses.
Pardon me.
St.Ack
P.S. Where on the hudson screen do you see the queue of patches to run?
I don't seem to be able to find it. Thanks.
Nigel Daley wrote:
Please do not keep resubmitting the same patch. The patches are in the
queue (and will now be run twice). You can see the build server is
doing something here:
http://lucene.zones.apache.org:8080/hudson/
The Patch build has been hanging since last week on
TestMiniMRWithDFS. I'll look into it today. The queue has 13 builds
in it currently
On Jun 11, 2007, at 9:50 AM, stack (JIRA) wrote:
[
https://issues.apache.org/jira/browse/HADOOP-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-1465:
--------------------------
Status: In Progress (was: Patch Available)
Retrying. Hudson ran v2 of patch, not v3.
Add cluster stop/start scripts for hbase
----------------------------------------
Key: HADOOP-1465
URL: https://issues.apache.org/jira/browse/HADOOP-1465
Project: Hadoop
Issue Type: New Feature
Components: contrib/hbase
Reporter: stack
Assignee: stack
Priority: Minor
Attachments: clusterscripts-v2.patch,
clusterscripts-v3.patch, clusterscripts.patch
Add start-hbase.sh and stop-hbase.sh scripts that will do for hbase
what *-dfs.sh does for HDFS and *-mapred.sh does for MR.
--This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
