Hi all, There are several integration test jobs failing where the docker container run by Testcontainers gets terminated with error code 137 (maps to out of memory error).
The failing jobs are: CI - Integration - Sql - https://github.com/apache/pulsar/actions/workflows/ci-integration-sql.yaml (most fail) CI - Integration - Process - https://github.com/apache/pulsar/actions/workflows/ci-integration-process.yaml (some succeed) CI - Integration - Messaging - https://github.com/apache/pulsar/actions/workflows/ci-integration-messaging.yaml (some succeed) CI - Integration - Function & IO - https://github.com/apache/pulsar/actions/workflows/ci-integration-function.yaml (some succeed) This started happening yesterday for most PR builds. For example: https://github.com/apache/pulsar/runs/3111868662?check_suite_focus=true#step:14:1024 Error: Tests run: 22, Failures: 1, Errors: 0, Skipped: 21, Time elapsed: 292.035 s <<< FAILURE! - in TestSuite Error: testPythonWordCountFunction(org.apache.pulsar.tests.integration.functions.PulsarStateTest) Time elapsed: 43.416 s <<< FAILURE! org.apache.pulsar.tests.integration.docker.ContainerExecException: /pulsar/bin/pulsar-admin functions querystate --tenant public --namespace default --name test-wordcount-py-fn-tfhycxsf --key message-1 failed on 705ecb067214d1cc42cd16358df6fa6d7a8cacc6c5ddd0cdde84a73b3e2e1f76 with error code 137 at org.apache.pulsar.tests.integration.utils.DockerUtils$2.onComplete(DockerUtils.java:248) at org.testcontainers.shaded.com.github.dockerjava.core.exec.AbstrAsyncDockerCmdExec$1.onComplete(AbstrAsyncDockerCmdExec.java:51) at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:276) at java.base/java.lang.Thread.run(Thread.java:829) I also ran an experiment in my own fork with a very old commit from 13 days ago (experiment is https://github.com/lhotari/pulsar/pull/47). The build failed in the same way. Therefore it doesn't seem to be caused by commits in the master branch. I'll try to debug the issue locally as the next step. BR, -Lari
