Skip to content

PreCommit Python Formatter #17685

PreCommit Python Formatter

PreCommit Python Formatter #17685

Triggered via schedule September 8, 2024 21:03
Status Success
Total duration 13m 42s
Artifacts
Matrix: beam_PreCommit_PythonFormatter
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
beam_PreCommit_PythonFormatter (Run PythonFormatter PreCommit)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
beam_PreCommit_PythonFormatter (Run PythonFormatter PreCommit)
Failed to save cache entry with path '/home/runner/.gradle/caches/jars-*/*,zstd-without-long,1.0' and key: instrumented-jars-70504779a05b171144156af9e079cba6: Error: Cache service responded with 429 during upload chunk.
beam_PreCommit_PythonFormatter (Run PythonFormatter PreCommit)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
beam_PreCommit_PythonFormatter (Run PythonFormatter PreCommit)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
beam_PreCommit_PythonFormatter (Run PythonFormatter PreCommit)
Failed to save cache entry with path '/home/runner/.gradle/caches/modules-*/files-*/*/*/*/*,zstd-without-long,1.0' and key: dependencies-e54eadec4312d39f35a5b73088d214a3: Error: Cache service responded with 429 during upload chunk.
beam_PreCommit_PythonFormatter (Run PythonFormatter PreCommit)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
beam_PreCommit_PythonFormatter (Run PythonFormatter PreCommit)
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/