[
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.
Some hudson configurations need more time to run the testsuite
--------------------------------------------------------------
Key: HSEARCH-496
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496
Project: Hibernate Search
Issue Type: Sub-task
Reporter: Sanne Grinovero
Assignee: Juraci Paixao Krohling
Fix For: 3.2.0.CR1
At least the configurations db2v91,mysql5,sybase15 fail because of timeout, the process
is killed by Hudson.
I believe they could succeed if somebody could reconfigure Hudson to give some more time.
--
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