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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/04 18:18:10 UTC

[GitHub] [beam] damccorm opened a new issue, #20616: ./gradlew check fails on a clean clone of Beam

damccorm opened a new issue, #20616:
URL: https://github.com/apache/beam/issues/20616

   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)
   
   Imported from Jira [BEAM-11402](https://issues.apache.org/jira/browse/BEAM-11402). Original Jira may contain additional context.
   Reported by: bhulette.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org