You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Ruan Hang (Jira)" <ji...@apache.org> on 2025/11/10 02:06:00 UTC

[jira] [Updated] (FLINK-32753) Print JVM flags on AZP

     [ https://issues.apache.org/jira/browse/FLINK-32753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruan Hang updated FLINK-32753:
------------------------------
    Fix Version/s: 2.3.0
                       (was: 2.2.0)

> Print JVM flags on AZP
> ----------------------
>
>                 Key: FLINK-32753
>                 URL: https://issues.apache.org/jira/browse/FLINK-32753
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System / Azure Pipelines
>    Affects Versions: 2.1.0
>            Reporter: Zakelly Lan
>            Assignee: Zakelly Lan
>            Priority: Minor
>              Labels: pull-request-available, stale-assigned
>             Fix For: 2.3.0
>
>
> I suggest printing JVM flags before the tests run, which could help investigate the test failures (especially memory or GC related issue). An example of pipeline output [here|https://dev.azure.com/lzq82555906/flink-for-Zakelly/_build/results?buildId=122&view=logs&j=9dc1b5dc-bcfa-5f83-eaa7-0cb181ddc267&t=511d2595-ec54-5ab7-86ce-92f328796f20&l=165]. You may search 'JVM information' in this log.



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