[
https://issues.apache.org/jira/browse/PARQUET-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278684#comment-17278684
]
ASF GitHub Bot commented on PARQUET-1971:
-----------------------------------------
gszadovszky commented on pull request #863:
URL: https://github.com/apache/parquet-mr/pull/863#issuecomment-773149581
Thanks, @wangyum for checking this. Also, I am not sure about the related
test anyway. That percentage of validating the limit was already changed 3
times.
I am fine with both ways. If you think the upgrading of the jdk8 version is
a better solution feel free to create another PR for this jira and I am happy
to review/push it.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Flaky test in github action
> ---------------------------
>
> Key: PARQUET-1971
> URL: https://issues.apache.org/jira/browse/PARQUET-1971
> Project: Parquet
> Issue Type: Bug
> Affects Versions: 1.12.0
> Reporter: Gabor Szadovszky
> Assignee: Gabor Szadovszky
> Priority: Major
>
> It seems we have a flaky test in the newly configured github action. It is
> strange that this test was not flaky in Travis. Anyway:
> {code}
> testMemoryManagerUpperLimit(org.apache.parquet.hadoop.TestMemoryManager):
> Pool size should be within 10% of the expected value (expected = 453745044
> actual = 505046624)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
