[ https://issues.apache.org/jira/browse/FLINK-25480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-25480: ----------------------------------- Labels: auto-deprioritized-critical stale-major test-stability (was: auto-deprioritized-critical test-stability) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Create dashboard/monitoring to see resource usage per E2E test > -------------------------------------------------------------- > > Key: FLINK-25480 > URL: https://issues.apache.org/jira/browse/FLINK-25480 > Project: Flink > Issue Type: Improvement > Components: Test Infrastructure > Affects Versions: 1.13.6, 1.14.3, 1.15.0 > Reporter: Martijn Visser > Priority: Major > Labels: auto-deprioritized-critical, stale-major, test-stability > > Over the past couple of weeks, we've encountered multiple problems with tests > failing due to out-of-memory errors and/or exit code 137 happening. These are > happening both on Alibaba CI machines, as well as Azure hosted agents. For > the Alibaba CI machines, we've mitigated the problem by reducing the number > of workers per CI machine from 7 to 5. These workers can spin up multiple > Docker containers, especially with Testcontainers getting used more and more. > If we can get insights in the resource usage per end-to-end test, it will > also help in debugging test infrastructure problems more quickly. -- This message was sent by Atlassian Jira (v8.20.10#820010)