[ 
https://issues.apache.org/jira/browse/FLINK-23154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthias updated FLINK-23154:
-----------------------------
    Description: We refactored the {{PackagedProgramRetriever}} class hierarchy 
as part of FLINK-21445. As part of this, I added some tests for the Python path 
but didn't look too deep into how to set up the flink python opt folder within 
the test infrastructure. As a consequence, I removed the tests again. But it 
might be worth it adding tests for loading the Python driver.  (was: We 
refactored the {{PackagedProgramRetriever}} class hierarchy as part of 
FLINK-21445. As part of this, I added some tests for the Python path but didn't 
look to deep into how to set up the flink python opt folder within the test 
infrastructure. Instead, I added {{Assume}} calls.

This ticket is about removing these {{Assume}} calls and implementing the tests 
properly.

It affects testss in {{FromJarEntryClassInformationProviderTest}} and 
{{PackagedProgramRetrieverImplTest}}.

--

The corresponding code changes are still subject to change and are currently 
under review in a [draft PR for 
FLINK-21445|https://github.com/apache/flink/pull/16286].)

> Fix Python PackagedProgramRetrieverImplTest implementations
> -----------------------------------------------------------
>
>                 Key: FLINK-23154
>                 URL: https://issues.apache.org/jira/browse/FLINK-23154
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Python
>            Reporter: Matthias
>            Priority: Major
>
> We refactored the {{PackagedProgramRetriever}} class hierarchy as part of 
> FLINK-21445. As part of this, I added some tests for the Python path but 
> didn't look too deep into how to set up the flink python opt folder within 
> the test infrastructure. As a consequence, I removed the tests again. But it 
> might be worth it adding tests for loading the Python driver.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to