You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2018/05/17 18:06:00 UTC

[jira] [Created] (KUDU-2445) AdminCliTest.TestUnsafeChangeConfigWithMultiplePendingConfigs is flaky

Adar Dembo created KUDU-2445:
--------------------------------

             Summary: AdminCliTest.TestUnsafeChangeConfigWithMultiplePendingConfigs is flaky
                 Key: KUDU-2445
                 URL: https://issues.apache.org/jira/browse/KUDU-2445
             Project: Kudu
          Issue Type: Bug
          Components: test
    Affects Versions: 1.8.0
            Reporter: Adar Dembo
         Attachments: kudu-admin-test.txt

Saw this in a TSAN pre-commit build. The failure was in a run of the Kudu CLI, but I don't see any stdout/stderr that would hint at what the failure was:
{noformat}
/home/jenkins-slave/workspace/kudu-master/2/src/kudu/tools/kudu-admin-test.cc:1096: Failure
Failed
Bad status: Runtime error: /tmp/dist-test-task4QLboq/build/tsan/bin/kudu: process exited with non-zero status 1{noformat}
I'm attaching the full test log.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)