You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/02/05 17:15:04 UTC
[jira] [Commented] (BEAM-11402) ./gradlew check fails on a clean
clone of Beam
[ https://issues.apache.org/jira/browse/BEAM-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279815#comment-17279815 ]
Beam JIRA Bot commented on BEAM-11402:
--------------------------------------
This issue was marked "stale-assigned" and has not received a public comment in 7 days. It is now automatically unassigned. If you are still working on it, you can assign it to yourself again. Please also give an update about the status of the work.
> ./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
>
> 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)