[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Emmanuel Bernard reassigned HSEARCH-496: ---------------------------------------- Assignee: Juraci Paixao Krohling (was: Emmanuel Bernard) I think it's more a temporary glitch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Juraci Paixao Krohling commented on HSEARCH-496: ------------------------------------------------ I can do that, but it's currently set to 90 minutes, which is more than enough IMO. We had problems of locking before, specially for exceptions which happens in transaction and are not rolled back properly (like HSEARCH-401). Also, I've seen some problems happening on a few tests which uses "int" where it should use AtomicInteger, as it's accessed by many threads (I couldn't find the JIRA for that). But if you think the tests are correct and that they just need some more time, I'll be glad to change it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Sanne Grinovero commented on HSEARCH-496: ----------------------------------------- Oh; 90 minutes is a lot more than needed, they run locally in 40 seconds. Sorry I don't see timestamps on Hudson. Maybe you could find out what it's waiting on? I'm not aware of int/AtomicInteger issues? Also WorkDuplicationTest, were it appears to be stuck, doesn't look like a multithreaded test. I'll check to see if the SessionFactory isn't closed; still it's weird that the HSQLDB configuration doesn't ever fail on the same tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Strong Liu commented on HSEARCH-496: ------------------------------------ I just ran the whole h-search test on our internal qa01 test server(it has faster db connection than my local) ----- ------------------------------------------------------- T E S T S ------------------------------------------------------- Running example.IndexAndSearchTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.413 sec Results : Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar] [INFO] Building jar: /qa/home/stliu/hibernate/search-trunk/hibernate-search-archetype/target/hibernate-search-archetype-3.2.0-SNAPSHOT.jar [INFO] [install:install] [INFO] Installing /qa/home/stliu/hibernate/search-trunk/hibernate-search-archetype/target/hibernate-search-archetype-3.2.0-SNAPSHOT.jar to /home/stliu/.m2/repository/org/hibernate/hibernate-search-archetype/3.2.0-SNAPSHOT/hibernate-search-archetype-3.2.0-SNAPSHOT.jar [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] ------------------------------------------------------------------------ [INFO] Hibernate Search Parent ............................... SUCCESS [8.651s] [INFO] Hibernate Search ...................................... SUCCESS [16:31.543s] [INFO] Hibernate Search Testing .............................. SUCCESS [1.395s] [INFO] Hibernate Search Archetype ............................ SUCCESS [11.112s] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 16 minutes 54 seconds [INFO] Finished at: Wed Apr 07 07:24:51 EDT 2010 [INFO] Final Memory: 42M/254M -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Emmanuel Bernard commented on HSEARCH-496: ------------------------------------------ Strong, your link does not work (cannot find hudson.qa.jboss.com). I am supposedly logged in the VPN, is that expected? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Juraci Paixao Krohling commented on HSEARCH-496: ------------------------------------------------ Emmanuel: I know there's an issue with DNS and some hosts inside the network. Could you try to replace the hostname with its IP (10.16.88.204) ? Strong: It's better to run the tests from inside an IDE. It takes longer, but you can watch the logs to see where it is being locked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Juraci Paixao Krohling commented on HSEARCH-496: ------------------------------------------------ I just ran the testsuite in my local machine inside Eclipse, using PostgreSQL as the database and I got a locking issue in the test NestedEmbeddedTest. From what I could see, it's because some databases (PostgreSQL included) have implicit transaction marking, but you still have to commit/rollback it. I wrapped last part of the test inside a transaction and it passed. But I wonder why you are not getting this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Emmanuel Bernard commented on HSEARCH-496: ------------------------------------------ I've applied your patch, it made sense. Should we close this bug entry? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Juraci Paixao Krohling updated HSEARCH-496: ------------------------------------------- Attachment: HSEARCH-496-2.diff It was still locking, in the same test. It seems that the other test (testNestedEmbeddedIndexingWithContainedInOnCollection) still have the same problem. Attached is a new patch which solves it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496?pag... ] Strong Liu commented on HSEARCH-496: ------------------------------------ now it hangs on org.hibernate.search.test.jgroups.common.JGroupsCommonTest.teradown methond 13:18:17,155 DEBUG SchemaExport:377 - drop table TShirt what causes this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira