damccorm commented on PR #29835: URL: https://github.com/apache/beam/pull/29835#issuecomment-1883860240
> > > > Will be curious anyone else's thoughts. > > > > As I understand it, this PR is fine - from a code perspective. BUT, introduces an issue due to some of our testing infrastructure. Not that a test 'fails' but rather a limitation in something we rely on. > > > > I'm inclined to merge the PR, and then address the limitations in the testing infra afterwards [ if it were to persist ]. Thoughts? > > > > > > > > > I agree with this. > > > @damccorm do you have any reservations on merging? > > > > > > Where is the failed check? If the test infra is flaky then I agree we shouldn't block on it. If we are turning a meaningful suite permared then I think we should address that before proceeding. Looking at the current pr, I only see the [failing Kafka check](https://github.com/apache/beam/actions/runs/7463358132/job/20307911415?pr=29835) which looks like it is running into a timeout (maybe its stuck)? We likely should not ignore that > > Also see --> [#29835 (comment)](https://github.com/apache/beam/pull/29835#issuecomment-1865913328) > > `Error: Error processing result file: CData section too big found, ...` > > Seems to be an issue with a limitation on `EnricoMi/publish-unit-test-result-action@v2` ...? > Oh I see - this silently failed and the workflow still succeeded. Yeah, I think this is fine to ignore. Its actually not a new issue (e.g. a scheduled run on master ran into this earlier today - https://github.com/apache/beam/actions/runs/7458106150) > Since an issue filed, it also seems like we can proceed, and see whether this is a persistent or flaky problem, and then prioritize fixing if warranted -- rather than being a blocker. Have we actually filed the issue? I don't see one referenced in the comments and couldn't find one -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
