zentol commented on PR #19733: URL: https://github.com/apache/flink/pull/19733#issuecomment-1127539634
> So I'm suspecting it's something that starts before this test that uses more disk space. But that just takes a long time to debug due to the run times. Have you considered copying/calling into the bash utils to log the environment info after each test? > We thought so too, but the error message is shown immediately when this test is starting. OK that's fair. `Elasticsearch6SinkE2ECase.testScaleDown` ran just fine though before the failing test. Are we doing any cleanup in between individual test cases? Since the next test (`testBasicSink`) indeed fails immediately does it mean we _right there_ crossed the disk space threshold? (that'd be quite the coincidence) We know we had 2gb available when the test started, since testcontainers checks that: `Docker environment should have more than 2GB free disk space` What is the test using those for? side-note: Is there a ticket for having the test only use a limited number of retries? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
