You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/11/02 16:16:50 UTC
[GitHub] [beam] ryanthompson591 opened a new issue, #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
ryanthompson591 opened a new issue, #23944:
URL: https://github.com/apache/beam/issues/23944
https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/
There are a variety of tests failing, and each run has a different failure.
However, after looking through it seems that test_pardo_large_input is one of the more commonly failing tests.
Here's a link to the logs for one of the failures [test_pardo_large_input](https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/6311/consoleFull)
--
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
[GitHub] [beam] ryanthompson591 commented on issue #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
Posted by GitBox <gi...@apache.org>.
ryanthompson591 commented on issue #23944:
URL: https://github.com/apache/beam/issues/23944#issuecomment-1303663170
@damccorm after sickbaying these tests can we close this?
--
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
[GitHub] [beam] TheNeuralBit commented on issue #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
Posted by GitBox <gi...@apache.org>.
TheNeuralBit commented on issue #23944:
URL: https://github.com/apache/beam/issues/23944#issuecomment-1302604305
Yeah it seems likely this is related to #21643. I'd suggest just tracking this as one flake rather than having the separate issue for non-cython environments
--
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
[GitHub] [beam] damccorm commented on issue #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
Posted by GitBox <gi...@apache.org>.
damccorm commented on issue #23944:
URL: https://github.com/apache/beam/issues/23944#issuecomment-1347044813
#22321 has some extra context
--
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
[GitHub] [beam] TheNeuralBit commented on issue #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
Posted by GitBox <gi...@apache.org>.
TheNeuralBit commented on issue #23944:
URL: https://github.com/apache/beam/issues/23944#issuecomment-1305713626
Generally when we sickbay tests we keep the issue open to track resolving the flakiness and re-enabling the test. We've debated a lot on how to set the priority for a test in that state. My opinion: the priority should be the same as if feature under test were broken, since we don't have evidence to the contrary.
--
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
[GitHub] [beam] damccorm commented on issue #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
Posted by GitBox <gi...@apache.org>.
damccorm commented on issue #23944:
URL: https://github.com/apache/beam/issues/23944#issuecomment-1302593488
I've been hitting this, with many runs ending with `NotImplementedError: Invalid PaneInfoEncoding: 6` (e.g. https://ci-beam.apache.org/job/beam_PreCommit_Python_Phrase/3240/testReport/apache_beam.runners.portability.fn_api_runner.fn_runner_test/FnApiRunnerTestWithGrpcAndMultiWorkers/test_pardo_large_input_5/)
I've also been seeing similarish errors with [test_batch_pardo_trigger_flush](https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/6321/testReport/apache_beam.runners.portability.fn_api_runner.fn_runner_test/FnApiRunnerTestWithGrpcAndMultiWorkers/test_batch_pardo_trigger_flush/)
@TheNeuralBit any ideas? Is this related to https://github.com/apache/beam/issues/21643? I'm going to put up a pr to temporarily disable both
--
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
[GitHub] [beam] ryanthompson591 commented on issue #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
Posted by GitBox <gi...@apache.org>.
ryanthompson591 commented on issue #23944:
URL: https://github.com/apache/beam/issues/23944#issuecomment-1300808904
.add-labels P1,bug,build
--
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
[GitHub] [beam] kennknowles commented on issue #23944: beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky
Posted by GitBox <gi...@apache.org>.
kennknowles commented on issue #23944:
URL: https://github.com/apache/beam/issues/23944#issuecomment-1379410152
If this is disabled, is it masking potential problems? Or if it is just disabled and we are not worried about correctness it could be P2.
--
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