[
https://issues.apache.org/jira/browse/FLINK-37843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954135#comment-17954135
]
Mika Naylor edited comment on FLINK-37843 at 5/26/25 5:32 PM:
--------------------------------------------------------------
This looks to be because the dev dependency for protobuf is
{{{}protobuf>=3.19.0{}}}, which resolves to different versions for Python 3.8
and Python 3.12. 3.12 resolves to {{5.26.1}} but 3.8 resolves to {{4.25.1.}}
This means when the tests are run against 3.8, it thinks the protos need to be
regenerated as there are code differences.
I'll open a PR to fix the protobuf version to a static version to prevent this
kind of drift and regenerate the protos.
was (Author: JIRAUSER308097):
This looks to be because the dev dependency for protobuf is
{{{}protobuf>=3.19.0{}}}, which resolves to different versions for Python 3.8
and Python 3.12. 3.9 and above resolve to {{5.26.1}} but 3.8 resolves to
{{4.25.1.}} This means when the tests are run against 3.8, it thinks the protos
need to be regenerated as there are code differences.
I'll open a PR to fix the protobuf version to a static version to prevent this
kind of drift and regenerate the protos.
> FlinkFnExecutionTests::test_flink_fn_execution_pb2_synced test failed of
> azure ci
> ---------------------------------------------------------------------------------
>
> Key: FLINK-37843
> URL: https://issues.apache.org/jira/browse/FLINK-37843
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Affects Versions: 2.1.0
> Reporter: dalongliu
> Priority: Major
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=67790&view=logs&j=9cada3cb-c1d3-5621-16da-0f718fb86602&t=0a887b12-e4d0-528d-2191-73222db51fda
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
