You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The integration test logs for v1 templates are not appearing in the Java PR git action or any other git action. One can see logs for v2 templates. For example, the dataflow job link log appears only for v2 template tests and not v1.
Example: ExportPipelineIT is test for Cloud_Spanner_to_GCS_Avro v1 template
There is only one line log containing ExportPipelineIT telling that 4 tests have passed.
But for any flex template ITs ex: BigtableChangeStreamsToGcsIT test forBigtable_Change_Streams_to_Google_Cloud_Storage
There are logs including dataflow job link. For many v1 templates. Could not find logs for any.
The task here is to investigate where is the gap to cause incomplete v1 template test logs, and fix it to align with v2 templates.
Relevant log output
The text was updated successfully, but these errors were encountered:
Related Template(s)
N/A
Template Version
N/A
What happened?
The integration test logs for v1 templates are not appearing in the Java PR git action or any other git action. One can see logs for v2 templates. For example, the dataflow job link log appears only for v2 template tests and not v1.
https://github.com/GoogleCloudPlatform/DataflowTemplates/actions/runs/12808415943/job/35712185387
Example: ExportPipelineIT is test for Cloud_Spanner_to_GCS_Avro v1 template
There is only one line log containing ExportPipelineIT telling that 4 tests have passed.
But for any flex template ITs ex: BigtableChangeStreamsToGcsIT test forBigtable_Change_Streams_to_Google_Cloud_Storage
There are logs including dataflow job link. For many v1 templates. Could not find logs for any.
The task here is to investigate where is the gap to cause incomplete v1 template test logs, and fix it to align with v2 templates.
Relevant log output
The text was updated successfully, but these errors were encountered: