You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2020/12/04 18:03:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Kenneth Knowles updated BEAM-11402:
-----------------------------------
    Status: Open  (was: Triage Needed)

> ./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
>            Assignee: Brian Hulette
>            Priority: 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-4831. 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)