[
https://issues.apache.org/jira/browse/FLINK-32753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-32753:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> 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, stale-assigned
> 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)
