You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "github-actions[bot] (via GitHub)" <gi...@apache.org> on 2025/02/05 00:49:05 UTC
[I] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
github-actions[bot] opened a new issue, #33859:
URL: https://github.com/apache/beam/issues/33859
The PostCommit Java ValidatesRunner ULR is failing over 50% of the time.
Please visit https://github.com/apache/beam/actions/workflows/beam_PostCommit_Java_ValidatesRunner_ULR.yml?query=is%3Afailure+branch%3Amaster to see all failed workflow runs.
See also Grafana statistics: http://metrics.beam.apache.org/d/CTYdoxP4z/ga-post-commits-status?orgId=1&viewPanel=3&var-Workflow=PostCommit%20Java%20ValidatesRunner%20ULR
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "aIbrahiim (via GitHub)" <gi...@apache.org>.
aIbrahiim commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4462574115
agree with [@Abacn](https://github.com/Abacn)’s read. This isnt a ULR specific javasdk special case but it’s the generic Python proto coder path failing on beam:coder:schema:v1 because Python doesn’t register that URN yet, after Java started emitting it via ModelCoderRegistrar ([#37631](https://github.com/apache/beam/pull/37631)).
[#38497](https://github.com/apache/beam/pull/38497) (excluding the two PerKeyOrderingTest methods in ULR) unblocks CI, but any portable Java pipeline that puts SchemaCoder in the proto and runs on the Python job service can hit the same KeyError
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "aIbrahiim (via GitHub)" <gi...@apache.org>.
aIbrahiim commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4462579443
agree with [@Abacn](https://github.com/Abacn) as this isnt a ULR specific javasdk special case but it’s the generic Python proto coder path failing on beam:coder:schema:v1 because Python doesn’t register that URN yet, after Java started emitting it via ModelCoderRegistrar (https://github.com/apache/beam/pull/37631).
https://github.com/apache/beam/pull/38497 (excluding the two PerKeyOrderingTest methods in ULR) unblocks CI, but any portable Java pipeline that puts SchemaCoder in the proto and runs on the Python job service can hit the same KeyError
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "acrites (via GitHub)" <gi...@apache.org>.
acrites commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-5374707537
I added some comments to https://github.com/apache/beam/pull/39594, but the gist is, I think I found out how to get Python to not try to create the Schema coder.
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "shunping (via GitHub)" <gi...@apache.org>.
shunping closed issue #33859: The PostCommit Java ValidatesRunner ULR job is flaky
URL: https://github.com/apache/beam/issues/33859
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto closed issue #33859: The PostCommit Java ValidatesRunner ULR job is flaky
URL: https://github.com/apache/beam/issues/33859
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-2636016121
Possible cause: https://github.com/apache/beam/pull/33385
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4443606007
`PerKeyOrderingTest > testMultipleStatefulOrderingWithShuffle FAILED
java.lang.RuntimeException at PerKeyOrderingTest.java:282
PerKeyOrderingTest > testMultipleStatefulOrderingWithoutShuffle FAILED
java.lang.RuntimeException at PerKeyOrderingTest.java:323`
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4443100085
Reopening since the workflow is still flaky
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "kennknowles (via GitHub)" <gi...@apache.org>.
kennknowles commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-5320126040
For a coder that Python doesn't understand, is there a standard way that the data is just carried along as bytes?
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4533757821
Reopening since the workflow is still flaky
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4478587797
Fixed by #38514 in release branch
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn closed issue #33859: The PostCommit Java ValidatesRunner ULR job is flaky
URL: https://github.com/apache/beam/issues/33859
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4420507300
Stabilized
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-3625124659
Stabilized
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4462409236
> Does the ULR special case "javasdk" coders and now that it is a different URN that is unknown to the ULR it is presuming it is a known coder? That's a ULR bug. It should be resilient to unknown coders that have URNs.
The code path is generic, happens when translating a coder from proto
```
File "/runner/_work/beam/beam/sdks/python/apache_beam/runners/portability/fn_api_runner/execution.py", line 783, in _enqueue_stage_initial_inputs
coder = self.pipeline_context.coders[self.safe_coders.get(
File "/runner/_work/beam/beam/sdks/python/apache_beam/runners/pipeline_context.py", line 155, in __getitem__
return self.get_by_id(id)
File "/runner/_work/beam/beam/sdks/python/apache_beam/runners/pipeline_context.py", line 103, in get_by_id
self._id_to_obj[id] = self._obj_type.from_runner_api(
File "/runner/_work/beam/beam/sdks/python/apache_beam/coders/coders.py", line 364, in from_runner_api
[context.coders.get_by_id(c) for c in coder_proto.component_coder_ids],
File "/runner/_work/beam/beam/sdks/python/apache_beam/coders/coders.py", line 364, in <listcomp>
[context.coders.get_by_id(c) for c in coder_proto.component_coder_ids],
File "/runner/_work/beam/beam/sdks/python/apache_beam/runners/pipeline_context.py", line 103, in get_by_id
self._id_to_obj[id] = self._obj_type.from_runner_api(
File "/runner/_work/beam/beam/sdks/python/apache_beam/coders/coders.py", line 364, in from_runner_api
[context.coders.get_by_id(c) for c in coder_proto.component_coder_ids],
File "/runner/_work/beam/beam/sdks/python/apache_beam/coders/coders.py", line 364, in <listcomp>
[context.coders.get_by_id(c) for c in coder_proto.component_coder_ids],
File "/runner/_work/beam/beam/sdks/python/apache_beam/runners/pipeline_context.py", line 103, in get_by_id
self._id_to_obj[id] = self._obj_type.from_runner_api(
File "/runner/_work/beam/beam/sdks/python/apache_beam/coders/coders.py", line 364, in from_runner_api
[context.coders.get_by_id(c) for c in coder_proto.component_coder_ids],
File "/runner/_work/beam/beam/sdks/python/apache_beam/coders/coders.py", line 364, in <listcomp>
[context.coders.get_by_id(c) for c in coder_proto.component_coder_ids],
File "/runner/_work/beam/beam/sdks/python/apache_beam/runners/pipeline_context.py", line 103, in get_by_id
self._id_to_obj[id] = self._obj_type.from_runner_api(
File "/runner/_work/beam/beam/sdks/python/apache_beam/coders/coders.py", line 361, in from_runner_api
parameter_type, constructor = cls._known_urns[coder_proto.spec.urn]
KeyError: 'beam:coder:schema:v1'
```
Technically any runners that have Java side ended up with a schema coder then get consumed in python side could trigger the same issue?
These tests happen to expose this issue. The same test was explicitly excluded from other runners (Flink/Spark/twister2 has all excluded "UsesPerKeyOrderedDelivery"), while Python validate runner test do not have corresponding tests, persumably could also break if it does
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4414458751
Reopening since the workflow is still flaky
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn closed issue #33859: The PostCommit Java ValidatesRunner ULR job is flaky
URL: https://github.com/apache/beam/issues/33859
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-3620885315
Reopening since the workflow is still flaky
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto closed issue #33859: The PostCommit Java ValidatesRunner ULR job is flaky
URL: https://github.com/apache/beam/issues/33859
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "liferoad (via GitHub)" <gi...@apache.org>.
liferoad closed issue #33859: The PostCommit Java ValidatesRunner ULR job is flaky
URL: https://github.com/apache/beam/issues/33859
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "shunping (via GitHub)" <gi...@apache.org>.
shunping commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4446518151
Discussed with @acrites, we will sickbay those tests since the new URN is currently only supported in dataflow.
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "kennknowles (via GitHub)" <gi...@apache.org>.
kennknowles commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4461872559
(but also can we just wipe out the Python ULR? this is a test that the Python local runner can run a Java pipeline)
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Amar3tto (via GitHub)" <gi...@apache.org>.
Amar3tto commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-2636031023
@rohitsinha54 ptal
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "aIbrahiim (via GitHub)" <gi...@apache.org>.
aIbrahiim commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4445776742
I investigated the failure and i think the root cause appears to be this change in this pr #37631 https://github.com/apache/beam/pull/37631/changes#diff-eb787a9abab531331fb0cd79a99c06746dbb7468fae3b42cd6fe70ea47898894R144
as the failing tests PerKeyOrderingTest.testMultipleStatefulOrdering happens in the Python job service while reconstructing coders from the pipeline proto: python KeyError: beam:coder:schema:v1
so after this change java started emitting the portable URN:
beam:coder:schema:v1
for SchemaCoder via ModelCoderRegistrar.
however this URN is currently only implemented on the java side but Python sdk doesn't register or recognize this coder URN yet so when the ULR (which uses the Python job service) receives the pipeline proto, coder deserialization fails during lookup
so the regression is effectively:
java emits schema:v1
python cannot deserialize schema:v1
cc: @acrites @damccorm @Abacn @Amar3tto
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4460837804
Reopened: https://github.com/apache/beam/pull/38497#issuecomment-4460818350
--
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] The PostCommit Java ValidatesRunner ULR job is flaky [beam]
Posted by "kennknowles (via GitHub)" <gi...@apache.org>.
kennknowles commented on issue #33859:
URL: https://github.com/apache/beam/issues/33859#issuecomment-4461869069
Does the ULR special case "javasdk" coders and now that it is a different URN that is unknown to the ULR it is presuming it is a known coder? That's a ULR bug. It should be resilient to unknown coders that have URNs.
--
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