Thanks Brian, Ismael!
Benjamín (@benWize) opened PR https://github.com/apache/beam/pull/14275
PostCommit checks are working
https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_SparkStructuredStreaming_PR/64/
Just a heads up in case someone else from the dev team would like to tak
Actually there are many reasons that could have produced this
regression even if the code of the runner has not changed at all: (1)
those tests weren't enabled before and now are and they weren't
passing or (2) the tests were changed or (3) my principal guess: the
translation strategy of a runners-
You can look through the history of the PostCommit [1]. We only keep a
couple weeks of history, but it looks like we have one successful run from
Sept 10, 2020, marked as "keep forever", that ran on commit
57055262e7a6bff447eef2df1e6efcda754939ca.
Is that what you're looking for?
(Somewhat related
Hi team,
it is mentioned in this WI that the tests (GroupByKeyTest
testLargeKeys100MB and testGroupByKeyWithBadEqualsHashCode) stopped working
around five months ago.
I took a look at the PRs prior to that date and couldn't find a report
stating that they were working.
Is there a way to get report
