Invoke teardown when DoFn throws in portable runners #3298
Annotations
2 errors and 7 warnings
|
Publish JUnit Test Results
lxml.etree.XMLSyntaxError: Memory allocation failed : Huge input lookup, line 46460, column 61174
|
|
Publish JUnit Test Results:
runners/samza/job-server/build/test-results/validatesPortableRunnerEmbedded/TEST-org.apache.beam.sdk.transforms.ViewTest.xml#L1
Error processing result file: Memory allocation failed : Huge input lookup, line 46460, column 61174 (TEST-org.apache.beam.sdk.transforms.ViewTest.xml, line 46460)
|
|
Post Setup environment
Failed to save cache entry with path '/home/runner/.gradle/caches/jars-*/*,zstd-without-long,1.0' and key: instrumented-jars-ffc69e8b9463b28d330341196ee2fe02: Error: Cache service responded with 429 during upload chunk.
|
|
Post Setup environment
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with ESPIPE: invalid seek, read
|
|
Post Setup environment
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
|
|
Post Setup environment
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
|
|
Post Setup environment
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
|
|
Post Setup environment
Failed to save cache entry with path '/home/runner/.gradle/caches,/home/runner/.gradle/notifications,/home/runner/.gradle/.gradle-build-action,zstd-without-long,1.0' and key: v8-gradle|Linux|postcommit java pvr samza-beam_PostCommit_Java_PVR_Samza[df9801c6dedf1c5434802feee2810a12]-c9aa996fd5c9579b2ac1f9e11db539daf60e5b02: Error: Cache service responded with 429 during upload chunk.
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/
|
Loading