I resubmitted it to Hudson. If it hangs again, I'll get a thread dump before I kill it.

Cheers,
Nige

On Jul 13, 2007, at 4:10 PM, Michael Stack wrote:

Nigel Daley wrote:
I had to kill TestTableMapReduce on the patch build since it had hung.


TestTableMapReduce is a long-running test. Its 2 minutes on a local machine (To be addressed). But looking at console output, org.apache.hadoop.fs.TestCopyFiles fails first with an Error. My patch builds locally fine (I just retried it).

What would you suggest I do Nigel?  Should I try a resubmit?

Thanks,
St.Ack





On Jul 13, 2007, at 2:54 PM, Hadoop QA (JIRA) wrote:


[ https://issues.apache.org/jira/browse/HADOOP-1574? page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#action_12512633 ]

Hadoop QA commented on HADOOP-1574:
-----------------------------------

-1, build or testing failed

2 attempts failed to build and test the latest attachment http:// issues.apache.org/jira/secure/attachment/12361753/hadoop-1574- v7.patch against trunk revision r555813.

Test results: http://lucene.zones.apache.org:8080/hudson/job/ Hadoop-Patch/406/testReport/ Console output: http://lucene.zones.apache.org:8080/hudson/job/ Hadoop-Patch/406/console

Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.

[hbase] Concurrent creates of a table named 'X' all succeed
-----------------------------------------------------------

                Key: HADOOP-1574
URL: https://issues.apache.org/jira/browse/ HADOOP-1574
            Project: Hadoop
         Issue Type: Bug
         Components: contrib/hbase
           Reporter: stack
           Assignee: stack
           Priority: Minor
Attachments: duptable-v2.patch, duptable-v3.patch, duptable.patch, hadoop-1574-v4.patch, hadoop-1574-v5.patch, hadoop-1574-v7.patch


If multiple threads all try to create a table of a particular, all succeed. It makes for a mess. Create table needs to be synchronized so only one thread creates a table and subsequent threads fail with 'table already exits'. The test for pre-existence also needs fixing.

--This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.




Reply via email to