[
https://issues.apache.org/jira/browse/BEAM-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278223#comment-17278223
]
Beam JIRA Bot commented on BEAM-11404:
--------------------------------------
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.
> 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
> Labels: stale-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)
