Bug 885995 - org.infinispan.distribution.rehash.L1OnRehashDisabledTest.testInvalidationBehaviorOnRehash randomly fails
Summary: org.infinispan.distribution.rehash.L1OnRehashDisabledTest.testInvalidationBeh...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR2
: 6.2.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-11 09:31 UTC by Anna Manukyan
Modified: 2025-02-10 03:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:27:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-2618 0 Major Resolved org.infinispan.distribution.rehash.L1OnRehashDisabledTest.testInvalidationBehaviorOnRehash randomly fails 2017-01-16 14:36:52 UTC

Description Anna Manukyan 2012-12-11 09:31:22 UTC 
You can find the failing logs here: 

http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite-rhel/jdk=openjdk-1.7.0-local,label=RHEL6_x86_64/60/testReport/org.infinispan.distribution.rehash/L1OnRehashDisabledTest/testInvalidationBehaviorOnRehash/

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/edg-60-ispn-testsuite-windows/jdk=java17_default,label=dev98-W2k8r2-x86_64/12/testReport/org.infinispan.distribution.rehash/L1OnRehashDisabledTest/testInvalidationBehaviorOnRehash/
Comment 3 JBoss JIRA Server 2013-07-15 09:44:50 UTC 
Dan Berindei <dberinde> updated the status of jira ISPN-2618 to Resolved
Comment 4 JBoss JIRA Server 2013-07-15 09:44:50 UTC 
Dan Berindei <dberinde> made a comment on jira ISPN-2618

The test has never failed in CI since we switched to TeamCity.
Comment 5 Red Hat Bugzilla 2025-02-10 03:27:08 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.