[
https://issues.apache.org/jira/browse/BEAM-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315731#comment-17315731
]
Beam JIRA Bot commented on BEAM-11402:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> ./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: P2
> Labels: beam-fixit, stale-P2
>
> 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)
