[ http://jira.jboss.com/jira/browse/JBCACHE-1387?page=all ] Brian Stansberry updated JBCACHE-1387: -------------------------------------- Priority: Minor (was: Major) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBCACHE-1387?page=com.atlassian.jira.p... ] Manik Surtani commented on JBCACHE-1387: ---------------------------------------- Can this be closed? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBCACHE-1387?page=com.atlassian.jira.p... ] Brian Stansberry commented on JBCACHE-1387: ------------------------------------------- Run showed 2 failures: http://hudson.qa.jboss.com/hudson/job/jboss-cache-core-2.2.X-jbossas/org.... This one showed up on a recent run of the standard JBC profile, so I doubt it has anything to do with the different dependencies in the JBossAS profile. http://hudson.qa.jboss.com/hudson/job/jboss-cache-core-2.2.X-jbossas/org.... Not sure about this. Manik, do you see transient failures of this test? I didn't see any in a quick look at the last 5 or so runs of the standard testsuite w/ JDK 5. Only significant differences in the JBossAS profile are the JGroups version and the version of JBossTS. Kinda hard to imagine they would break that one test and nothing else. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira