[FLINK-34267] Python connector test fails when running on MacBook with m1 processor

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: API / Python, Build System / CI, Connectors / Common
• Labels: pull-request-available

Environment

m1 MacBook Pro

MacOS 14.2.1

• Assignee: Aleksandr Pilipenko
• Reporter: Aleksandr Pilipenko
• Created: 29/Jan/24 21:25
• Updated: 09/Feb/24 10:01
• Resolved: 09/Feb/24 10:00

Description

Attempt to execute lint_python.sh on m1 macbook fails while trying to install miniconda environment

=============installing environment=============
installing wget...
install wget... [SUCCESS]
installing miniconda...
download miniconda...
download miniconda... [SUCCESS]
installing conda...
tail: illegal offset -- +000000000000018838: Invalid argument
tail: illegal offset -- +000000000000018838: Invalid argument
/Users/apilipenko/Dev/flink-connector-aws/flink-python/dev/download/miniconda.sh: line 353: /Users/apilipenko/Dev/flink-connector-aws/flink-python/dev/.conda/preconda.tar.bz2: No such file or directory
upgrade pip...
./dev/lint-python.sh: line 215: /Users/apilipenko/Dev/flink-connector-aws/flink-python/dev/.conda/bin/python: No such file or directory
upgrade pip... [SUCCESS]
install conda ... [SUCCESS]
install miniconda... [SUCCESS]
installing python environment...
installing python3.7...
./dev/lint-python.sh: line 247: /Users/apilipenko/Dev/flink-connector-aws/flink-python/dev/.conda/bin/conda: No such file or directory
conda install 3.7 retrying 1/3
./dev/lint-python.sh: line 254: /Users/apilipenko/Dev/flink-connector-aws/flink-python/dev/.conda/bin/conda: No such file or directory
conda install 3.7 retrying 2/3
./dev/lint-python.sh: line 254: /Users/apilipenko/Dev/flink-connector-aws/flink-python/dev/.conda/bin/conda: No such file or directory
conda install 3.7 retrying 3/3
./dev/lint-python.sh: line 254: /Users/apilipenko/Dev/flink-connector-aws/flink-python/dev/.conda/bin/conda: No such file or directory
conda install 3.7 failed after retrying 3 times.            You can retry to execute the script again.

Issue Links

• links to: GitHub Pull Request #34