Hi Team, When running the CTest command

ctest -R flb-rt-out_elasticsearch -V

with the latest Fluent Bit release 5.0.3, the test failed with the error

Test interrupted by SIGSEGV

. Notably, this same test case passed successfully when we used Fluent Bit 4.2.3. Considering the difference in behavior between the two versions, we were wondering if this could possibly be a regression bug in release 5.0.3? thanks

64: Test response_success...                        [2026/04/29 07:28:33.465] [ info] [fluent bit] version=5.0.3, commit=, pid=85\n64: [2026/04/29 07:28:33.465] [ info] [storage] ver=1.5.4, type=memory, sync=normal, checksum=off, max_chunks_up=128\n64: [2026/04/29 07:28:33.465] [ info] [simd    ] SSE2\n64: [2026/04/29 07:28:33.465] [ info] [cmetrics] version=2.1.2\n64: [2026/04/29 07:28:33.465] [ info] [ctraces ] version=0.7.1\n64: [2026/04/29 07:28:33.465] [ info] [input:lib:lib.0] initializing\n64: [2026/04/29 07:28:33.465] [ info] [input:lib:lib.0] storage_strategy='memory' (memory only)\n64: [2026/04/29 07:28:33.465] [ info] [sp] stream processor started\n64: [2026/04/29 07:28:33.465] [ info] [engine] Shutdown Grace Period=1, Shutdown Input Grace Period=0\n64: [2026/04/29 07:28:33.466] [ info] [output:es:es.0] worker #0 started\n64:   Test interrupted by SIGSEGV.\n64: Test response_successes...                      [2026/04/29 07:28:33.873] [ info] [fluent bit] version=5.0.3, commit=, pid=90\n64: [2026/04/29 07:28:33.873] [ info] [storage] ver=1.5.4, type=memory, sync=normal, checksum=off, max_chunks_up=128\n64: [2026/04/29 07:28:33.873] [ info] [simd    ] SSE2\n64: [2026/04/29 07:28:33.873] [ info] [cmetrics] version=2.1.2\n64: [2026/04/29 07:28:33.873] [ info] [ctraces ] version=0.7.1\n64: [2026/04/29 07:28:33.873] [ info] [input:lib:lib.0] initializing\n64: [2026/04/29 07:28:33.873] [ info] [input:lib:lib.0] storage_strategy='memory' (memory only)\n64: [2026/04/29 07:28:33.873] [ info] [sp] stream processor started\n64: [2026/04/29 07:28:33.873] [ info] [engine] Shutdown Grace Period=1, Shutdown Input Grace Period=0\n64:   Test interrupted by SIGSEGV.\n64: Test response_partially_success...              [2026/04/29 07:28:34.176] [ info] [fluent bit] version=5.0.3, commit=, pid=95\n64: [2026/04/29 07:28:34.176] [ info] [storage] ver=1.5.4, type=memory, sync=normal, checksum=off, max_chunks_up=128\n64: [2026/04/29 07:28:34.176] [ info] [simd    ] SSE2\n64: [2026/04/29 07:28:34.176] [ info] [cmetrics] version=2.1.2\n64: [2026/04/29 07:28:34.176] [ info] [ctraces ] version=0.7.1\n64: [2026/04/29 07:28:34.176] [ info] [input:lib:lib.0] initializing\n64: [2026/04/29 07:28:34.176] [ info] [input:lib:lib.0] storage_strategy='memory' (memory only)\n64: [2026/04/29 07:28:34.177] [ info] [sp] stream processor started\n64: [2026/04/29 07:28:34.177] [ info] [engine] Shutdown Grace Period=1, Shutdown Input Grace Period=0\n64:   Test interrupted by SIGSEGV.\n64: FAILED: 3 of 17 unit tests have failed.\n1/1 Test #64: flb-rt-out_elasticsearch .........***Failed   43.07 sec\n\n0% tests passed, 1 tests failed out of 1\n\nLabel Time Summary:\nruntime    =  43.07 sec*proc (1 test)\n\nTotal Test time (real) =  43.10 sec\n\nThe following tests FAILED:\n\t 64 - flb-rt-out_elasticsearch (Failed)\n", errors: b'Errors while running CTest\nOutput from these tests are in: /src/build/Testing/Temporary/LastTest.log\nUse "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.\n'