[
https://issues.apache.org/jira/browse/FLINK-32753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zakelly Lan updated FLINK-32753:
--------------------------------
Description: 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. (was: I suggest printing JVM
flags before the tests run, which could help investigate the test failures
(especially memory or GC related issue). An example:
[https://dev.azure.com/lzq82555906/42941eae-0335-452a-89c5-bd6a71809dc9/_apis/build/builds/122/logs/157]
. You may search 'JVM information' in this log.)
> 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
> Reporter: Zakelly Lan
> Assignee: Zakelly Lan
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.18.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)
