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

Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2020/12/04 23:28:00 UTC

[jira] [Updated] (BEAM-11404) Consider running :test precommits in a hermetic environment

     [ https://issues.apache.org/jira/browse/BEAM-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Hulette updated BEAM-11404:
---------------------------------
    Status: Open  (was: Triage Needed)

> Consider running :test precommits in a hermetic environment
> -----------------------------------------------------------
>
>                 Key: BEAM-11404
>                 URL: https://issues.apache.org/jira/browse/BEAM-11404
>             Project: Beam
>          Issue Type: Task
>          Components: testing
>            Reporter: Brian Hulette
>            Priority: P2
>
> :test tasks should generally just run unit tests or fast running tests that use an in-memory (or containerized) fake, but it can be tempting to write simple tests that leverage production cloud services, and not classify them as integration tests (e.g. BEAM-11363). We should have some automation to protect against this - we can run :test tasks in a hermetic environment in precommits.
> One possible approach: use a docker container with networking disable (maybe re-use the Beam developer container BEAM-10891)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)