[
https://issues.jboss.org/browse/SEAMJCR-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646590#comment-12646590
]
Marek Schmidt commented on SEAMJCR-24:
--------------------------------------
Increasing it to 60 seconds doesn't seem to make a difference. The error
happens consistently with ~50% probability on jenkins slaves. I cannot
reproduce it locally. This is just a wild guess, but is it possible that the
event isn't observed if it was fired on some different background thread? That
would explain why I can only reproduce it on jenkins slaves, which are all >1
CPU.
> JcrCDIEventListenerJackrabbitTest sometimes fails on Jenkins
> ------------------------------------------------------------
>
> Key: SEAMJCR-24
> URL: https://issues.jboss.org/browse/SEAMJCR-24
> Project: Seam JCR
> Issue Type: Bug
> Components: JackRabbit Integration
> Affects Versions: 3.1.0.Beta4, 3.1.0.Beta5
> Reporter: Marek Schmidt
> Attachments:
> org.jboss.seam.jcr.test.common.events.JcrCDIEventListenerJackrabbitTest.testOnEventAdded.txt
>
>
> JcrCDIEventListenerJackrabbitTest sometimes fails on Jenkins,
> A comment in the test reads:
> {noformat}
> // ModeShape uses background threads for event firing and similar
> // activities.
> // let's give it 5 seconds to run, then check the bags.
> Thread.sleep(5000);
> // Check that node was added
> assertEquals(1, counter.getCountForType(Event.NODE_ADDED));
> {noformat}
> so perhaps the 5 seconds limit is just not enoough?
> Also note the attached log in which it appears the repository had been shut
> down before the assertion was made, which might suggest that waiting longer
> probably wouldn't help and that the event just didn't happen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
