kennknowles commented on pull request #11792:
URL: https://github.com/apache/beam/pull/11792#issuecomment-658426050
OK this is known flake https://issues.apache.org/jira/browse/BEAM-10470 in
`JdbcDriverTest`, totally unrelated to this and shouldn't even be running. At
this point I feel
kennknowles commented on pull request #11792:
URL: https://github.com/apache/beam/pull/11792#issuecomment-658385268
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
kennknowles commented on pull request #11792:
URL: https://github.com/apache/beam/pull/11792#issuecomment-658384672
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
kennknowles commented on pull request #11792:
URL: https://github.com/apache/beam/pull/11792#issuecomment-658384859
(it could have been interrupted, I didn't dig too deep)
This is an automated message from the Apache Git
kennknowles commented on pull request #11792:
URL: https://github.com/apache/beam/pull/11792#issuecomment-657760388
Flakes in this run:
- https://issues.apache.org/jira/browse/BEAM-10474 failure in py
DisplayDataTest
And then I just introduced an actual compile error in my
kennknowles commented on pull request #11792:
URL: https://github.com/apache/beam/pull/11792#issuecomment-656448609
https://ci-beam.apache.org/job/beam_PreCommit_Python_Commit/13653/ appears
to be a failure in unrelated code. It does not look like something that would
flake. Perhaps
