TeeTime issueshttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues2017-08-15T13:06:25+02:00https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/347Fix concurrency bug in DynamicDistributorTest.shouldWorkWithCreateActionTrigg...2017-08-15T13:06:25+02:00Christian WulfFix concurrency bug in DynamicDistributorTest.shouldWorkWithCreateActionTriggers()```java
java.lang.AssertionError:
Expected: is <[2]>
but: was <[2]>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
...```java
java.lang.AssertionError:
Expected: is <[2]>
but: was <[2]>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at teetime.stage.basic.distributor.dynamic.DynamicDistributorTest.assertValuesForIndex(DynamicDistributorTest.java:119)
at teetime.stage.basic.distributor.dynamic.DynamicDistributorTest.shouldWorkWithCreateActionTriggers(DynamicDistributorTest.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
```Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/326Add Default Scheduler for Pipes2017-04-26T14:37:22+02:00Sören HenningAdd Default Scheduler for PipesSee TeeTime Benchmarks projectSee TeeTime Benchmarks projecthttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/321Validate stages created at runtime2017-03-21T10:21:59+01:00Christian WulfValidate stages created at runtimeVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/293Fix taskfarm tests2017-08-03T12:59:05+02:00Nelson Tavares de SousaFix taskfarm testsAfter #291 , some tests of the taskfarm do not work anymore (neither before), as the ExtractionTestPipe is set before ``connectPorts`` is calledAfter #291 , some tests of the taskfarm do not work anymore (neither before), as the ExtractionTestPipe is set before ``connectPorts`` is calledhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/285Make the signal tests work again2016-09-08T16:41:50+02:00Christian WulfMake the signal tests work againVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/284DivideAndConquerStageTest runs infinitely2017-08-03T12:58:57+02:00Christian WulfDivideAndConquerStageTest runs infinitelyVersion 3.0https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/244Active consumer with multiple input ports may never terminate2016-02-22T11:09:26+01:00Nelson Tavares de SousaActive consumer with multiple input ports may never terminateSuppose a consumer stage with more than one input port is used.
The remaining ports must be handled manually by the programmer. This could potentially lead to non-terminating stage, as the terminating signal from the remaining ports w...Suppose a consumer stage with more than one input port is used.
The remaining ports must be handled manually by the programmer. This could potentially lead to non-terminating stage, as the terminating signal from the remaining ports will never arrive the stage. See [`TerminationTest.terminatesMultiInputPort()`](https://build.se.informatik.uni-kiel.de/gitlab/teetime/teetime/blob/master/src/test/java/teetime/framework/TerminationTest.java#L35) which illustrates this bug.