damccorm commented on code in PR #35297:
URL: https://github.com/apache/beam/pull/35297#discussion_r2155141138
##########
sdks/python/setup.py:
##########
@@ -391,10 +388,8 @@ def get_portability_package_data():
# 3. Exclude protobuf 4 versions that leak memory, see:
# https://github.com/apache/beam/issues/28246
'protobuf>=3.20.3,<6.0.0.dev0,!=4.0.*,!=4.21.*,!=4.22.0,!=4.23.*,!=4.24.*', #
pylint: disable=line-too-long
- 'pydot>=1.2.0,<2',
Review Comment:
> would this line (Task :sdks:python:test-suites:tox:py312:testPython312 )
in the log good enough to identify the environment? or would you choose a
different strategy to identify the environment?
Yeah, that's what I usually use, and then you can look at the gradle task.
An alternative at the failed test log, you can see something like:
```
________________________ YamlMappingTest.test_validate
_________________________
[gw1] linux -- Python 3.9.22
/runner/_work/beam/beam/sdks/python/test-suites/tox/py39/build/srcs/sdks/python/target/.tox-py39-cloud/py39-cloud/bin/python
...
```
Tox will create a folder with the task name (in this case py39-cloud) as
part of the path name. So in this case, the task is py39-cloud -
https://github.com/apache/beam/blob/9d75411a3bd085351e6283b556e067fa4e467b35/sdks/python/tox.ini#L99
You'll also see this task show up elsewhere in the logs (e.g. tox-py39-cloud
shows up a bunch of places). An llm probably could figure it out too, but I
haven't tried it yet :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@beam.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
