geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-485) CI failure: DeltaSizingDUnitTest.testClientWithCloning
Date Wed, 28 Oct 2015 18:44:27 GMT

    [ https://issues.apache.org/jira/browse/GEODE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978989#comment-14978989
] 

ASF GitHub Bot commented on GEODE-485:
--------------------------------------

GitHub user sboorlagadda opened a pull request:

    https://github.com/apache/incubator-geode/pull/26

    Fixes GEODE-485. 

    Logging at debug level on a SocketException while closing the connection to avoid any
suspect strings written to logs.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sboorlagadda/incubator-geode feature/GEODE-409

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-geode/pull/26.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #26
    
----
commit 9957c6416a99004058ab242edc4f3b711d3cfaf0
Author: Dave Barnes <dbarnes@pivotal.io>
Date:   2015-10-21T22:58:48Z

    GEODE-465 changed 2 occurrences of PartionedResolver to PartitionResolver in Javadocs

commit d812f901033ec3819a5d715bb43380648ff83ef4
Author: Mark Bretl <mbretl@pivotal.io>
Date:   2015-10-26T18:26:54Z

    GEODE-487: Remove integrationTest and distributedTest from build task.
    
    This commit removes integrationTest and distributedTest tasks from the
    build task lifecycle. The tasks were associated with the 'check' task,
    which is in the 'build' lifecycle. After removing the tasks, only the
    'test' task is run when build task is executed.
    
    Tested by running 'clean build'
    
    Review available at https://reviews.apache.org/r/39664

commit 5412c641176327f8e48fbf9af69d64fe2e3bd2e7
Author: William Markito <wmarkito@pivotal.io>
Date:   2015-10-26T23:32:32Z

    GEODE-479 - Closing PR #23 bumping language level to Java 8

commit e4573db9333a7509d217be7372e3e3b90a978584
Author: Darrel Schneider <dschneider@pivotal.io>
Date:   2015-10-27T23:26:59Z

    GEODE-411: fix suspect string on disconnect
    
    DistributionManager now has a isCloseInProgress method
    that checks both the volatile closeInProgress boolean
    and ask its DistributedSystem if it is disconnecting.
    This new method is used in places that decide if a warning
    should be logged.

commit f6bceefe37133e06ea8da2eda33ce4b49af4b357
Author: Hitesh Khamesra <hkhamesra@pivotal.io>
Date:   2015-10-28T16:33:24Z

    GEODE-501. test no-ack region thus we need to wait before validating
    the results.

commit e7b0db1923d35acc0bea8c0e62cf6ba7b714a1e8
Author: Sai Boorlagadda <sboorlagadda@pivotal.io>
Date:   2015-10-28T18:37:49Z

    Fixes GEODE-485.
    * Loggin at debug level on a SocketException while closing the connection to avoid any
suspect strings written to logs.

----


> CI failure: DeltaSizingDUnitTest.testClientWithCloning
> ------------------------------------------------------
>
>                 Key: GEODE-485
>                 URL: https://issues.apache.org/jira/browse/GEODE-485
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Sai Boorlagadda
>            Assignee: Sai Boorlagadda
>              Labels: CI
>
> {noformat}
> Error Message
> java.lang.AssertionError: Suspicious strings were written to the log during this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 96
> java.net.SocketException: Broken pipe
> Stacktrace
> java.lang.AssertionError: Suspicious strings were written to the log during this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 96
> java.net.SocketException: Broken pipe
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307)
> 	at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:784)
> 	at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:759)
> 	at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:737)
> 	at junit.framework.TestCase.runBare(TestCase.java:146)
> 	at junit.framework.TestResult$1.protect(TestResult.java:122)
> 	at junit.framework.TestResult.runProtected(TestResult.java:142)
> 	at junit.framework.TestResult.run(TestResult.java:125)
> 	at junit.framework.TestCase.run(TestCase.java:129)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:252)
> 	at junit.framework.TestSuite.run(TestSuite.java:247)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> 	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> 	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> 	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> 	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> 	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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> 	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 	at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> 	at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> 	at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> 	at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> 	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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> 	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 	at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> 	at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> Standard Output
> Previously run tests: [DeltaPropagationStatsDUnitTest, RemoveAllDAckDUnitTest, PartitionedRegionEvictionDUnitTest,
DeltaSizingDUnitTest]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message