[
https://issues.apache.org/jira/browse/BEAM-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242773#comment-17242773
]
Brian Hulette commented on BEAM-11363:
--------------------------------------
There are additional tests that suffer from this. They appear to be GCP
integration tests, but have Test in the class name and so run under the :test
task:
DicomIOTest. test_Dicom_failedMetadataRead
FhirIOTest. test_FhirIO_failedReads
FhirIOTest. test_FhirIO_failedWrites
HL7v2IOTest. test_HL7v2IO_failedReads
HL7v2IOTest. test_HL7v2IO_failedWrites
Let's track those here as well.
> Integration tests are run under the test task
> ---------------------------------------------
>
> Key: BEAM-11363
> URL: https://issues.apache.org/jira/browse/BEAM-11363
> Project: Beam
> Issue Type: Bug
> Components: extensions-java-gcp
> Reporter: Niels Basjes
> Assignee: Brian Hulette
> Priority: P2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As found in [https://github.com/apache/beam/pull/13308] the
> [https://github.com/apache/beam/blob/40f517f9da8b2f0914f06493f8e042eeb2739578/sdks/java/extensions/ml/build.gradle#L47-L49]
> explicitly includes the integration tests in the test task.
> As a consequence it is now impossible to run the tests without a google GCP
> account as the build will fail over missing account information.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
