You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2017/03/02 15:13:45 UTC

[jira] [Updated] (EDGENT-219) new keyedTimeBatchWindowTest isn't robust?

     [ https://issues.apache.org/jira/browse/EDGENT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale LaBossiere updated EDGENT-219:
-----------------------------------
    Component/s: Test

> new keyedTimeBatchWindowTest isn't robust?
> ------------------------------------------
>
>                 Key: EDGENT-219
>                 URL: https://issues.apache.org/jira/browse/EDGENT-219
>             Project: Edgent
>          Issue Type: Test
>          Components: Test
>            Reporter: Dale LaBossiere
>
> From a recent travis-ci run, the test failed.  Presumably just a test timing sensitivity issue?  If so can it be desensitized?
>     [junit] Running quarks.test.window.WindowTest
>     [junit] Testsuite: quarks.test.window.WindowTest
>     [junit] Tests run: 10, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 39.843 sec
>     [junit] Tests run: 10, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 39.843 sec
>     [junit] 
>     [junit] Testcase: keyedTimeBatchWindowTest(quarks.test.window.WindowTest):	FAILED
>     [junit] Values:[219, 200, 200, 200, 200, 200, 200, 200, 200, 200]
>     [junit] junit.framework.AssertionFailedError: Values:[219, 200, 200, 200, 200, 200, 200, 200, 200, 200]
>     [junit] 	at quarks.test.window.WindowTest.keyedTimeBatchWindowTest(WindowTest.java:422)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)