You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/07/05 10:40:00 UTC
[jira] [Updated] (FLINK-27165) Benchmark test SerializationFrameworkMiniBenchmarks#serializerHeavyString became unstable
[ https://issues.apache.org/jira/browse/FLINK-27165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-27165:
-----------------------------------
Labels: stale-major test-stability (was: test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> Benchmark test SerializationFrameworkMiniBenchmarks#serializerHeavyString became unstable
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-27165
> URL: https://issues.apache.org/jira/browse/FLINK-27165
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks
> Affects Versions: 1.15.0, 1.16.0
> Reporter: Matthias Pohl
> Priority: Major
> Labels: stale-major, test-stability
>
> The benchmark test {{SerializationFrameworkMiniBenchmarks#serializerHeavyString}} became unstable mid of January 2022 which cannot be explained (see [graph|http://codespeed.dak8s.net:8000/timeline/#/?exe=1&ben=serializerHeavyString&extr=on&quarts=on&equid=off&env=2&revs=1000]).
> There is some suspicion that it was caused by FLINK-25246 because Java 11 was added during that time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)