suztomo edited a comment on pull request #13137: URL: https://github.com/apache/beam/pull/13137#issuecomment-813596393
@Aliraza-N The DiacomIOTest and other gcp healthcare service tests require default application credentials. > 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 https://issues.apache.org/jira/browse/BEAM-11363?focusedCommentId=17242773&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17242773 Exception: ``` Caused by: java.io.IOException: The Application Default Credentials are not available. They are available if running in Google Compute Engine. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information. at com.google.auth.oauth2.DefaultCredentialsProvider.getDefaultCredentials(DefaultCredentialsProvider.java:134) at com.google.auth.oauth2.GoogleCredentials.getApplicationDefault(GoogleCredentials.java:119) at com.google.auth.oauth2.GoogleCredentials.getApplicationDefault(GoogleCredentials.java:91) at org.apache.beam.sdk.io.gcp.healthcare.HttpHealthcareApiClient.initClient(HttpHealthcareApiClient.java:691) at org.apache.beam.sdk.io.gcp.healthcare.HttpHealthcareApiClient.<init>(HttpHealthcareApiClient.java:121) at org.apache.beam.sdk.io.gcp.healthcare.DicomIO$ReadStudyMetadata$FetchStudyMetadataFn.instantiateHealthcareClient(DicomIO.java:164) ``` Do you think they should be classified as integration tests? If not, is there a way to run this test in GitHub Actions? -- 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. For queries about this service, please contact Infrastructure at: [email protected]
