tvalentyn
tvalentyn
I think we should introduce additional extras, that would define allowed ranges for optional beam dependencies. Having many extras is very common in project that support a certain usecase on...
if you put: R: @arunpandianp in a comment instead of a PR description, bot shouldn't be confused.
> looks like the python 3.11 ML tests have some sort of setup issue (https://github.com/apache/beam/issues/31287) for now you can consider this a new suite that never worked.
our ml tests are in a bad shape, but they were not running extensively previously.
waiting on author
cc: @damccorm - we might want to prioritize https://github.com/apache/beam/issues/30908.
to repro: gradlew :sdks:python:test-suites:tox:py39:testPy39ML -Pposargs=apache_beam/ml/
Couldn't repro locally. `gradlew :sdks:python:yamlIntegrationTests` passed for me.
Python 3.11 tests ML tests are failing due to: https://github.com/apache/beam/issues/31287. We need to fix that too but it is not related to this change.
noting that all tests except https://github.com/apache/beam/actions/runs/9071465904/job/24956302074?pr=31282 passed, adding a fix for that suite now.