xVersionPolicyTest appears to be timing sensitive
Reported by Ben Hood | October 7th, 2010 @ 01:16 AM
Check out builds 530,531 on TC. I also came across a similar failure in the CorrelatedVersionPolicyTest when my local machine was under heavy load.
Comments and changes to this ticket
-
Paul Jones October 7th, 2010 @ 10:52 AM
The actual failure is:
CorrelatedVersionPolicyTest.shouldStoreUpstreamChangesToCorrelationStoreAndNotifySessionManagerWithoutLastUpdate (net.lshift.diffa.kernel.differencing) Unexpected method call versionStore.storeUpstreamVersion(VersionID(A-B,id1), 2010-07-08T09:17:00.000+01:00, 2010-10-07T01:05:12.322+01:00, "vsn1"): versionStore.storeUpstreamVersion(VersionID(A-B,id1), 2010-07-08T09:17:00.000+01:00, 2010-10-07T01:05:12.321+01:00, "vsn1"): expected: 1, actual: 0 java.lang.AssertionError: Unexpected method call versionStore.storeUpstreamVersion(VersionID(A-B,id1), 2010-07-08T09:17:00.000+01:00, 2010-10-07T01:05:12.322+01:00, "vsn1"): versionStore.storeUpstreamVersion(VersionID(A-B,id1), 2010-07-08T09:17:00.000+01:00, 2010-10-07T01:05:12.321+01:00, "vsn1"): expected: 1, actual: 0 -
Ben Hood October 7th, 2010 @ 08:44 PM
- Tag set to “tests”
This has also occurred on build 4, 25 and 35 (diffa) as well.
-
Ben Hood October 13th, 2010 @ 07:04 PM
- Milestone cleared.
-
Paul Jones October 15th, 2010 @ 09:10 AM
- State changed from “new” to “closed”
Resolved by making the test less time dependent, and allow a range of results.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood