jaketf commented on pull request #11339:
URL: https://github.com/apache/beam/pull/11339#issuecomment-629364334


   @mwalenia 
   > What exactly causes this 
error?https://builds.apache.org/job/beam_PostCommit_Java_PR/362/testReport/junit/org.apache.beam.sdk.io.gcp.healthcare/FhirIOWriteIT/testFhirIO_ExecuteBundle_R4_/
   
   potentially there was an issue staging all appropriate files
   ```
   May 14, 2020 2:05:45 AM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
   INFO: No stagingLocation provided, falling back to gcpTempLocation
   May 14, 2020 2:05:45 AM org.apache.beam.runners.dataflow.DataflowRunner 
fromOptions
   INFO: PipelineOptions.filesToStage was not specified. Defaulting to files 
from the classpath: will stage 183 files. Enable logging at DEBUG level to see 
which files will be staged.
   May 14, 2020 2:05:46 AM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
   INFO: No stagingLocation provided, falling back to gcpTempLocation
   May 14, 2020 2:05:46 AM org.apache.beam.runners.dataflow.DataflowRunner 
fromOptions
   INFO: PipelineOptions.filesToStage was not specified. Defaulting to files 
from the classpath: will stage 183 files. Enable logging at DEBUG level to see 
which files will be staged.
   May 14, 2020 2:05:46 AM 
org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory
 create
   INFO: No stagingLocation provided, falling back to gcpTempLocation
   May 14, 2020 2:05:46 AM org.apache.beam.runners.dataflow.DataflowRunner 
fromOptions
   INFO: PipelineOptions.filesToStage was not specified. Defaulting to files 
from the classpath: will stage 183 files. Enable logging at DEBUG level to see 
which files will be staged.
   ```


----------------------------------------------------------------
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]


Reply via email to