-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Failing Test]: beam_PostCommit_XVR_Direct perma-red. #28972
Comments
At this point it appears to be hard failing for a few Python 3.11 related issues. https://github.com/apache/beam/actions/runs/7803720204/job/21284093581
|
This is a regression in Beam 2.53.0. Unfortunately GHA logs expires in 3 months. From now one only knows the regression happens between Nov 8, 2023 (last successful run and https://github.com/apache/beam/actions/runs/7018120946) - Dec 8, 2023 #2111 (first run see this issue and still has log) |
CC: @robertwb |
For some reason the window in WindowedValue decoded here
is not a tuple of window objects, but a tuple of bytes e.g. The WIndowedValueCoder with BytesCoder as its window coder is constructed here: beam/sdks/python/apache_beam/coders/coders.py Line 392 in 1a05f39
so it's using the information from proto to construct the coder. |
This was exposed by apache#28972 when the set of "known" coders was inadvertently reduced.
This was exposed by apache#28972 when the set of "known" coders was inadvertently reduced.
What happened?
Seems like Go x-lang integration tests (for example, DebeziumIO, JDBCIO) are flaky.
For example,
https://ci-beam.apache.org/job/beam_PostCommit_XVR_Direct/4702/consoleFull
10:26:17 2023/10/10 17:25:26 🐳 Terminating container: 82fa13ab9230
10:26:17 containers.go:100: error terminating container: Error response from daemon: No such container: 82fa13ab92303fc01cc1db52f2cf67f1c9a7666cf3611cdd0bce58936fc8d232
10:26:17 --- FAIL: TestDebeziumIO_BasicRead (144.27s)
10:26:17 FAIL
We should probably convert this tests to use Prism runner to be stable.
Issue Failure
Failure: Test is flaky
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components
The text was updated successfully, but these errors were encountered: