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

Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2022/12/09 16:05:00 UTC

[jira] [Created] (FLINK-30355) crictl causes long wait in e2e tests

Matthias Pohl created FLINK-30355:
-------------------------------------

             Summary: crictl causes long wait in e2e tests
                 Key: FLINK-30355
                 URL: https://issues.apache.org/jira/browse/FLINK-30355
             Project: Flink
          Issue Type: Bug
          Components: Test Infrastructure, Tests
    Affects Versions: 1.17.0
            Reporter: Matthias Pohl


We observed strange behavior in the e2e test where the e2e test run times out: https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43824&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&s=ae4f8708-9994-57d3-c2d7-b892156e7812&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=7446

The issue seems to be related to {{crictl}} again because we see the following error message in multiple tests. No logs are produced afterwards for ~30mins resulting in the overall test run taking too long:
{code}
Dec 09 08:55:39 crictl
fatal: destination path 'cri-dockerd' already exists and is not an empty directory.
fatal: a branch named 'v0.2.3' already exists
mkdir: cannot create directory ‘bin’: File exists
Dec 09 09:26:41 fs.protected_regular = 0
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)