This kind of dependency can cause a flakey test? Seems like this kind of thing would be a consistent failure, at least that's what I am seeing as well
On Wed, Jan 23, 2019 at 11:11 AM Ruoyun Huang <ruo...@google.com> wrote: > I ran into the same issue. it is flaky, due to some depended package. > > short term solution is to rerun precommit. For me it was gone on second > try. > > On Wed, Jan 23, 2019 at 11:06 AM Alex Amato <ajam...@google.com> wrote: > >> https://jira.apache.org/jira/browse/BEAM-6495?filter=-2 >> >> Any ideas, how this got through the precommit? >> >> > Task :beam-sdks-java-extensions-sql:compileJava FAILED >> >> /usr/local/google/home/ajamato/go/src/ >> github.com/apache/beam/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/impl/JdbcFactory.java:29: >> error: cannot find symbol >> >> import >> org.apache.beam.sdk.extensions.sql.impl.parser.impl.BeamSqlParserImpl; >> >> ^ >> >> symbol: class BeamSqlParserImpl >> >> location: package org.apache.beam.sdk.extensions.sql.impl.parser.impl >> >> 1 error >> >> > > -- > ================ > Ruoyun Huang > >
