geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-3901) CI Failure:
Date Fri, 27 Oct 2017 16:34:00 GMT


ASF GitHub Bot commented on GEODE-3901:

jdeppe-pivotal opened a new pull request #988: GEODE-3901: Shut gfsh down cleanly so as not
to produce suspect messa…
   …ges in the log
   Thank you for submitting a contribution to Apache Geode.
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   ### For all changes:
   - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
   - [x] Has your PR been rebased against the latest commit within the target branch (typically
   - [x] Is your initial contribution a single, squashed commit?
   - [x] Does `gradlew build` run cleanly?
   - [ ] Have you written or updated unit tests to verify your changes?
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](
   ### Note:
   Please ensure that once the PR is submitted, you check travis-ci for build issues and
   submit an update to your PR as soon as possible. If you need help, please send an
   email to

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> CI Failure:
> -------------------------------------------------------------------------------------------------
>                 Key: GEODE-3901
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>            Reporter: Jens Deppe
>              Labels: ci
> {noformat}
> startLocatorAndImportOldClusterConfigZip FAILED
>     java.lang.AssertionError: Suspicious strings were written to the log during this
>     Fix the strings or use IgnoredException.addIgnoredException to ignore.
>     -----------------------------------------------------------------------
>     Found suspect string in log4j at line 9262
>     [fatal 2017/10/24 14:48:55.241 UTC <JMX client heartbeat 2> tid=0x928] (tid=2344
msgId=13) No longer connected to 46627f9139b9[28500].
> {noformat}

This message was sent by Atlassian JIRA

View raw message