MartijnVisser commented on PR #19733: URL: https://github.com/apache/flink/pull/19733#issuecomment-1127698748
> Have you considered copying/calling into the bash utils to log the environment info after each test? That already exists. There's usually around 20GB free when starting, see https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=35682&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=11b0df07-3e5e-58da-eb81-03003e470195&l=290 or https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=35664&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=11b0df07-3e5e-58da-eb81-03003e470195&l=290 as examples. When the Bash based tests end, it shows there is still around 12GB available. From a failed run: ``` 2022-05-14T05:19:06.6557479Z May 14 05:19:06 Filesystem Size Used Avail Use% Mounted on 2022-05-14T05:19:06.6558259Z May 14 05:19:06 /dev/root 90G 78G 12G 88% / ``` > Are we doing any cleanup in between individual test cases? I don't believe we are > side-note: Is there a ticket for having the test only use a limited number of retries? https://issues.apache.org/jira/browse/FLINK-27642 What I don't understand is why the `Elasticsearch6SinkE2ECase` is outputting so many log lines, compared to for example `SmokeKafkaITCase`. I've asked @alpreu if he can look into this. Created https://issues.apache.org/jira/browse/FLINK-27649 for that. Could we at least merge this band-aid, while fixing https://issues.apache.org/jira/browse/FLINK-27649 and https://issues.apache.org/jira/browse/FLINK-27642 -- 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]
