[
https://issues.apache.org/jira/browse/BEAM-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325982#comment-17325982
]
Beam JIRA Bot commented on BEAM-11402:
--------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> ./gradlew check fails on a clean clone of Beam
> ----------------------------------------------
>
> Key: BEAM-11402
> URL: https://issues.apache.org/jira/browse/BEAM-11402
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Brian Hulette
> Priority: P3
> Labels: beam-fixit
>
> Our contribution guide directs new contributors to run ./gradlew check after
> getting their environment setup, but its actually quite hard to do this.
> * There are a number of tests run under the :test task that actually access
> external services, and/or require some authentication to be setup (BEAM-11363)
> * There is often an issue with :sdk:go:goVet that looks like BEAM-4422. It
> seems flaky, perhaps its being broken by another task? Described some
> investigation
> [here|https://github.com/apache/beam/pull/13308#issuecomment-736955450]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
