zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nerdyyatrice <...@git.apache.org>
Subject [GitHub] zookeeper issue #167: commitProcessor does not crash when an unseen commit s...
Date Fri, 19 May 2017 20:18:13 GMT
Github user nerdyyatrice commented on the issue:

    Thanks Han, will do.  so do I still need to re-kick the Jenkins job?
    > On May 19, 2017, at 9:44 AM, Michael Han <notifications@github.com> wrote:
    > noCrashOnCommittedRequestsOfUnSeenRequestTest is failing here, please investigate.
    > https://builds.apache.org/job/ZooKeeper_UT_StressTest/4152/testReport/junit/org.apache.zookeeper.server.quorum/CommitProcessorConcurrencyTest/noCrashOnCommittedRequestsOfUnSeenRequestTest/
    > (This is a Jenkins job I set up to stress test unit test for specific pull request
    > —
    > You are receiving this because you were mentioned.
    > Reply to this email directly, view it on GitHub <https://github.com/apache/zookeeper/pull/167#issuecomment-302753487>,
or mute the thread <https://github.com/notifications/unsubscribe-auth/ALGPjBzwO5Ghp6KIMM2JNBNxO7Kc7ovSks5r7cb2gaJpZM4L85T6>.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message