[ https://forge.continuent.org/jira/browse/HEDERA-39?page=all ]
Linas Virbalas resolved HEDERA-39:
----------------------------------
Resolution: Fixed
GC selection was de-hardcoded from test classes. Now GC is selected via JVM
argument for both ViewChangeTest and ChannelPerformanceMultiprocessTest, eg.:
-Dproperties=/hedera_jgroups.properties
With this this task is accomplished.
> JUnit test for virtual synchrony
> --------------------------------
>
> Key: HEDERA-39
> URL: https://forge.continuent.org/jira/browse/HEDERA-39
> Project: Hedera
> Type: Sub-task
> Versions: Hedera 2.0
> Environment: JUnit
> Reporter: Linas Virbalas
> Assignee: Linas Virbalas
> Fix For: Hedera 2.0
>
> Original Estimate: 1 week
> Remaining: 1 week
>
> Tests are needed which would check whether virtual synchrony principle holds.
> Remarks:
> 1. View changes. Assume there is a group of members that randomly join and
> leave the view. Then a third party in the view would observe the following
> properties (safety conditions) on view change messages:
> 1.a. Every member "leave" message is preceded by a join message from the same
> member.
> 1.b. Leave and join messages for the same member must alternate.
> 2. Communication messages:
> 2.a. View changes must be ordered with respect to communication messages.
> 2.b. Members should join, send messages and leave. All members must receive
> messages in order and between join and leave events. Members which observed
> some member joining, sending messages and leaving, should receive identical
> messages from this member.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Hedera mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/hedera
