[
https://issues.apache.org/jira/browse/FLINK-40123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18116025#comment-18116025
]
Martijn Visser commented on FLINK-40123:
----------------------------------------
Also on master, nightly 2026-09-16, e2e_2_ci:
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=79133
{code}
Checking for exceptions...
Found exception in log files; printing first 500 lines; see full logs for
details:
...
[FAIL] 'Run kubernetes Materialized Table test' failed after 4 minutes and 31
seconds! Test exited with exit code 0 but the logs contained errors, exceptions
or non-empty .out files
{code}
The only line in the dumped log that matches is the S3A statistics WARN, and
every counter in it
is zero:
{code}
WARN org.apache.hadoop.fs.s3a.S3AInstrumentation [] - Closing output stream
statistics while data is still marked as pending upload in
OutputStreamStatistics{counters=((stream_write_exceptions_completing_upload=0)
... (stream_write_exceptions=0) ...
{code}
{{internal_check_logs_for_exceptions}} ends in {{grep -ic "exception"}}, so the
counter name
{{stream_write_exceptions}} is enough to fail the run. Adding 2.4.0 to affects.
> heck_logs_for_exceptions false-positives on S3A stream_write_exceptions
> counter, flaking test_kubernetes_materialized_table.sh
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-40123
> URL: https://issues.apache.org/jira/browse/FLINK-40123
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 2.3.0, 2.4.0
> Environment: Azure build 76427, task "Run e2e tests" (log 87).
>
> https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=76427
> Reporter: Shekhar Prasad Rajak
> Priority: Major
> Fix For: 2.3.1
>
>
> The e2e test Run kubernetes Materialized Table test
> (flink-end-to-end-tests/test-scripts/test_kubernetes_materialized_table.sh)
> intermittently fails even though the test logic itself
> succeeds:
> [FAIL] 'Run kubernetes Materialized Table test' failed after 4 minutes and
> 20 seconds!
> Test exited with exit code 0 but the logs contained errors, exceptions or
> non-empty .out files
> Note exit code 0 — the test passed; the failure is raised entirely by the
> post-run log scan.
>
> How to reproduce
> Run test_kubernetes_materialized_table.sh against a SeaweedFS/S3A-backed
> catalog store; whenever the S3AInstrumentation "Closing output stream
> statistics" WARN is logged, the run fails in
> the exception check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
