Skip to content

[yaml] Add use cases for Enrichment transform in YAML #22106

[yaml] Add use cases for Enrichment transform in YAML

[yaml] Add use cases for Enrichment transform in YAML #22106

Triggered via pull request December 13, 2024 18:23
@reeba212reeba212
synchronize #32289
Status Success
Total duration 27m 35s
Artifacts

beam_PreCommit_Python_Transforms.yml

on: pull_request_target
Matrix: beam_PreCommit_Python_Transforms
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
beam_PreCommit_Python_Transforms (Run Python_Transforms PreCommit 3.9)
Failed to save cache entry with path '/home/runner/.gradle/caches/jars-*/*,zstd-without-long,1.0' and key: instrumented-jars-674184d914e4869f50000f84e64440a7: Error: Cache service responded with 429 during upload chunk.
beam_PreCommit_Python_Transforms (Run Python_Transforms PreCommit 3.9)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with ESPIPE: invalid seek, read
beam_PreCommit_Python_Transforms (Run Python_Transforms PreCommit 3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/setup-java@v3, gradle/gradle-build-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/