The Open Anzo Project

Semantic Application Middleware

  • Home
  • Community
  • License
  • About
Sponsors
Cambridge Semantics Inc.

Ticket #261 (closed defect: fixed)

Opened 10 months ago

Last modified 10 months ago

Datasets notification count wrong for testDatasets

Reported by: jpbetz Assigned to: jpbetz
Priority: critical Milestone: 3.0 milestone1
Component: openanzo Version: 3.0
Keywords: intermittent Cc: ben

Description

java.util.concurrent.TimeoutException?: Timeout of 30000ms expired waiting for condition to be satisfied: junit.framework.AssertionFailedError?: expected:&1& but was:&2&

at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:277) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:195) at junit.framework.Assert.assertEquals(Assert.java:201) at org.openanzo.test.client.TestAnzoClientIntegration?$17.test(TestAnzoClientIntegration?.java:2095) at org.openanzo.client.test.AssertBlock?.run(AssertBlock?.java:25) at org.openanzo.client.test.TestUtilities?.waitFor(TestUtilities?.java:195) at org.openanzo.client.test.TestUtilities?.waitFor(TestUtilities?.java:177) at org.openanzo.client.test.TestUtilities?.waitFor(TestUtilities?.java:167) at org.openanzo.test.client.TestAnzoClientIntegration?.testDatasets(TestAnzoClientIntegration?.java:2093)

Change History

03/26/08 14:42:37 changed by jpbetz

(In [2020]) re #261

Remove poor mans attempt at a negative assertion notification test. This is no way to test such a condition.

03/26/08 14:44:42 changed by jpbetz

Remaining TODO:

Write a proper test to make sure notifications that should no arrive do not arrive?

Fix underlying bug, which is that a dataset listener receives notifications it should not receive.

03/26/08 15:22:23 changed by jpbetz

(In [2021]) re #261

Check for actual statements received by notification listener rather than statement count since left-over notifications from previous tests may show up and cause counts to be wrong.

03/26/08 15:24:33 changed by jpbetz

We should review all tests and make sure we don't have other cases where we blindly use statement counts to make sure notifications have arrived because left-over notification from previous tests can taint the results.

03/28/08 21:21:51 changed by jpbetz

  • status changed from new to closed.
  • resolution set to fixed.

Above comments are incorrect. There is not a intra-test notification issue--reset does stop replica updates from reaching future tests. The issue with testDatasets was that previous updates within the test were causing the replica update part of the test to fail. Ideally this would be two separate tests, r2021, however, does fix the problem so marking as closed.

  • Home
  • Community
  • License
  • About
Copyright © 2007 - 2008 OpenAnzo.org