Skip to content

LoadTests Java GBK SparkStructuredStreaming Batch #1171

LoadTests Java GBK SparkStructuredStreaming Batch

LoadTests Java GBK SparkStructuredStreaming Batch #1171

Triggered via schedule September 9, 2024 14:53
Status Success
Total duration 41m 25s
Artifacts
Matrix: beam_LoadTests_Java_GBK_SparkStructuredStreaming_Batch
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
beam_LoadTests_Java_GBK_SparkStructuredStreaming_Batch (Run Load Tests Java GBK SparkStructuredStreaming Batch)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
beam_LoadTests_Java_GBK_SparkStructuredStreaming_Batch (Run Load Tests Java GBK SparkStructuredStreaming Batch)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
beam_LoadTests_Java_GBK_SparkStructuredStreaming_Batch (Run Load Tests Java GBK SparkStructuredStreaming Batch)
Unhandled error in Gradle post-action - job will continue: Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
beam_LoadTests_Java_GBK_SparkStructuredStreaming_Batch (Run Load Tests Java GBK SparkStructuredStreaming Batch)
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|loadtests java gbk sparkstructuredstreaming batch-beam_LoadTests_Java_GBK_SparkStructuredStreaming_Batch[7538a060cc813ef32663ddba6605ffde]-2573106f3673eeb987874560778f50fdde03379f: Error: Cache service responded with 429 during upload chunk.
beam_LoadTests_Java_GBK_SparkStructuredStreaming_Batch (Run Load Tests Java GBK SparkStructuredStreaming Batch)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: 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/