It does not look flaky to me. It seems to be failing all the time. Did anything change with serialisation? Because test seems to expect entities with id = '1', whereas the actual used instance within pipeline starts with an id of 11 on my machine...
https://github.com/apache/beam/blob/master/sdks/java/io/kudu/src/test/java/org/apache/beam/sdk/io/kudu/KuduIOTest.java#L148 On Fri, Feb 22, 2019 at 6:26 PM Reuven Lax <re...@google.com> wrote: > It's a precommit test. Should we disable this test until it can be > diagnosed? > > On Thu, Feb 21, 2019 at 2:25 PM Kenneth Knowles <k...@google.com> wrote: > >> I don't see it in the postcommit history: >> https://builds.apache.org/job/beam_PreCommit_Java_Cron/977/testReport/org.apache.beam.sdk.io.kudu/KuduIOTest/history/ >> >> (URL assembled by trial and error and from Mikhail's prior sharing) >> >> Kenn >> >> On Thu, Feb 21, 2019 at 12:59 PM Reuven Lax <re...@google.com> wrote: >> >>> I'm finding the KuduIO tests to be extremely flaky. I've just ran Java >>> Presubmit three times in a row, and each time the KuduIO tests failed. How >>> can we improve this situation? >>> >>> Example failure: >>> >>> >>> https://builds.apache.org/job/beam_PreCommit_Java_Phrase/754/testReport/junit/org.apache.beam.sdk.io.kudu/KuduIOTest/testWrite/ >>> >>
