[jira] [Comment Edited] (FLINK-30831) Improving e2e test output in case errors/exceptions are found

["Flaviu Cicio (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-30831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768256#comment-17768256 ] 

Flaviu Cicio edited comment on FLINK-30831 at 9/23/23 9:55 AM:
---------------------------------------------------------------

[~mapohl] Can I have this ticket as my first one?


was (Author: JIRAUSER302297):
[~mapohl] Can I take this ticket as my first one?

> Improving e2e test output in case errors/exceptions are found
> -------------------------------------------------------------
>
>                 Key: FLINK-30831
>                 URL: https://issues.apache.org/jira/browse/FLINK-30831
>             Project: Flink
>          Issue Type: Improvement
>          Components: Test Infrastructure
>    Affects Versions: 1.17.0, 1.15.3, 1.16.1
>            Reporter: Matthias Pohl
>            Priority: Minor
>              Labels: auto-deprioritized-major, starter
>
> Some e2e tests parse the Flink logs for exceptions using {{grep}}. We then print the first 500 lines of the each log file in case an exception that shouldn't be ignored is found (see [internal_check_logs_for_exceptions|https://github.com/apache/flink/blob/c9e87fe410c42f7e7c19c81456d4212a58564f5e/flink-end-to-end-tests/test-scripts/common.sh#L449] or [check_logs_for_errors|https://github.com/apache/flink/blob/c9e87fe410c42f7e7c19c81456d4212a58564f5e/flink-end-to-end-tests/test-scripts/common.sh#L387]). Instead, we could use {{grep -C200}} to actually print the context of the exception.
> This would help especially in those situations where the exception doesn't appear in the first 500 lines.
> This issue does not necessarily only include the two aforementioned code locations. One should check the scripts for other code with a similar issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)