Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unreliable test in CompositeCommandTest #260

Open
manuel-mauky opened this issue Jun 10, 2015 · 5 comments
Open

unreliable test in CompositeCommandTest #260

manuel-mauky opened this issue Jun 10, 2015 · 5 comments
Assignees
Milestone

Comments

@manuel-mauky
Copy link
Collaborator

The tests in CompositeCommandTest are unreliable. While the code works in rare situations the tests are failing due to java.util.concurrent.TimeoutExceptions.

This needs to be fixed to get a stable and reliable build.

@manuel-mauky
Copy link
Collaborator Author

longRunningAsyncComposite(de.saxsys.mvvmfx.utils.commands.CompositeCommandTest)  Time elapsed: 5.264 sec  <<< ERROR!
java.util.concurrent.TimeoutException
    at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1763)
    at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1907)
    at de.saxsys.mvvmfx.utils.commands.CompositeCommandTest.longRunningAsyncComposite(CompositeCommandTest.java:242)
    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:497)
    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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    at com.cedarsoft.test.utils.CatchAllExceptionsRule$1.evaluate(CatchAllExceptionsRule.java:31)
    at org.junit.rules.RunRules.evaluate(RunRules.java:20)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
    at de.saxsys.javafx.test.JfxRunner.access$001(JfxRunner.java:18)
    at de.saxsys.javafx.test.JfxRunner.runChild(JfxRunner.java:51)
    at de.saxsys.javafx.test.JfxRunner.runChild(JfxRunner.java:18)
    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.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
    at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
    at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
    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:497)
    at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
    at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
    at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
    at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

@manuel-mauky
Copy link
Collaborator Author

@manuel-mauky manuel-mauky added this to the 1.3.1 milestone Jun 15, 2015
manuel-mauky added a commit that referenced this issue Jun 16, 2015
#260 small changes to (sometimes) failing test.
@manuel-mauky manuel-mauky modified the milestones: 1.4.0, 1.3.1 Jun 17, 2015
@manuel-mauky
Copy link
Collaborator Author

I have set the timeouts higher in the failing test. We will watch this issue to see if the test still breaks. I will let this issue open until more time has passed without failing builds.

@manuel-mauky
Copy link
Collaborator Author

@manuel-mauky
Copy link
Collaborator Author

The test is still fails from time to time. For this reason I've marked the test case with @Ignore. This test case really needs to be fixed.

manuel-mauky added a commit that referenced this issue Jul 6, 2015
#260 set failing test to ignore as a temporal fix
@manuel-mauky manuel-mauky modified the milestones: 1.5.0, 1.4.0 Sep 8, 2015
@manuel-mauky manuel-mauky modified the milestones: 1.6.0, 1.5.0 Jun 1, 2016
@manuel-mauky manuel-mauky modified the milestones: 1.7.0, 1.6.0 Jan 23, 2017
@manuel-mauky manuel-mauky modified the milestones: 1.7.0, 1.8.0 Sep 20, 2017
@manuel-mauky manuel-mauky modified the milestones: 1.8.0, 1.9.0 Dec 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants