You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "shunping (via GitHub)" <gi...@apache.org> on 2025/12/18 02:48:56 UTC
[I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
shunping opened a new issue, #37137:
URL: https://github.com/apache/beam/issues/37137
### What happened?
The workflow https://github.com/apache/beam/actions/workflows/beam_Playground_CI_Nightly.yml has been failing since the release of Beam 2.70.
Even though the PR #37134 from @derrickaw was merged in the master, the test workflow is always using the latest released beam to build the backend container. This also explains why it started to fail after 2.70 was released.
https://github.com/apache/beam/blob/8cc26a4be1fc54810a0e59afe65a7fcc671ef3c3/.github/workflows/beam_Playground_CI_Nightly.yml#L86
Fortunately, the playground website is not affected at the moment, because it is running on a snapshot image created before the culprit PR #36853.
<img width="2300" height="478" alt="Image" src="https://github.com/user-attachments/assets/44a34ecc-fc52-4e4a-9803-f7e1b8bab40c" />
### Issue Failure
Failure: Test is flaky
### Issue Priority
Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam YAML
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Infrastructure
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
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-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "tvalentyn (via GitHub)" <gi...@apache.org>.
tvalentyn commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-3894053578
without changes, results are taken from cache.
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #37137: [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0
URL: https://github.com/apache/beam/issues/37137
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "shunping (via GitHub)" <gi...@apache.org>.
shunping commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-3668116984
Maybe we can change the test workflow (https://github.com/apache/beam/actions/workflows/beam_Playground_CI_Nightly.yml) to run on master?
Otherwise, the workflow will remains red until the next release...
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-5280626629
This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-3687868042
yeah we have to skip 2.70.0, and add it to known issues for this version
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-3676475974
yeah we should run the workflow on master, or snapshot Beam SDK and containers then this could have been caught before a release.
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-3686767436
But what to do with the Update Beam Playground [process](https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-beam-playground)?
Release contains circular import bug, should we wait for 2.71.0?
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-4958372480
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "shunping (via GitHub)" <gi...@apache.org>.
shunping commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-3688463220
Yea. Looks like if we do not update the image used by for the playground, it will be fine.
I see the previous images do not have tag for 2.69, so it is probably fine to skip 2.70.
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Failing Test]: beam_Playground_CI_Nightly failed at 2.70.0 [beam]
Posted by "tvalentyn (via GitHub)" <gi...@apache.org>.
tvalentyn commented on issue #37137:
URL: https://github.com/apache/beam/issues/37137#issuecomment-3894044922
is see that Python playgroud examples don't work if i make any changes to them, however trivial. I am getting these errors:
```
Traceback (most recent call last):
File "/opt/playground/backend/executable_files/aaa1da65-53db-4af6-b69b-222efe999bc2/aaa1da65-53db-4af6-b69b-222efe999bc2.py", line 152, in <module>
main()
File "/opt/playground/backend/executable_files/aaa1da65-53db-4af6-b69b-222efe999bc2/aaa1da65-53db-4af6-b69b-222efe999bc2.py", line 128, in main
dot = pipeline_graph.PipelineGraph(p).get_dot()
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/interactive/display/pipeline_graph.py", line 113, in __init__
self._construct_graph(
File "/usr/local/lib/python3.10/site-packages/apache_beam/runners/interactive/display/pipeline_graph.py", line 240, in _construct_graph
self._graph = pydot.Dot()
NameError: name 'pydot' is not defined
```
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org