Skip to content

[Feature] Enable the capability to specify zstd and lz4 segment compression via config #28513

[Feature] Enable the capability to specify zstd and lz4 segment compression via config

[Feature] Enable the capability to specify zstd and lz4 segment compression via config #28513

Triggered via pull request September 16, 2024 21:11
Status Failure
Total duration 46m 20s
Artifacts

pinot_tests.yml

on: pull_request
Pinot Linter Test Set
0s
Pinot Linter Test Set
Matrix: compatibility-verifier
Matrix: integration-test
Matrix: multi-stage-compatibility-verifier
Matrix: quickstarts
Matrix: unit-test
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 2 warnings
Pinot Compatibility Regression Testing against release-1.0.0 on compatibility-verifier/sample-test-suite
The hosted runner encountered an error while running your job. (Error Type: Failure).
Pinot Quickstart on JDK 11-temurin with skip bytebuffers:false
The hosted runner encountered an error while running your job. (Error Type: Failure).
Pinot Unit Test Set 2 (temurin-21) with skip bytebuffers:true
The hosted runner: GitHub Actions 138 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Unit Test Set 1 (temurin-21) with skip bytebuffers:false
The hosted runner: GitHub Actions 115 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Multi-Stage Query Engine Compatibility Regression Testing against release-1.2.0 on compatibility-verifier/multi-stage-query-engine-test-suite
The hosted runner: GitHub Actions 41 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Quickstart on JDK 21-temurin with skip bytebuffers:true
The hosted runner: GitHub Actions 185 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Linter Test Set
The hosted runner: GitHub Actions 179 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Compatibility Regression Testing against master on compatibility-verifier/sample-test-suite
The hosted runner: GitHub Actions 279 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Multi-Stage Query Engine Compatibility Regression Testing against master on compatibility-verifier/multi-stage-query-engine-test-suite
The hosted runner: GitHub Actions 315 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Quickstart on JDK 21-temurin with skip bytebuffers:false
The hosted runner: GitHub Actions 403 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Integration Test Set 2 (temurin-11) with skip bytebuffers:false
The hosted runner: GitHub Actions 441 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Unit Test Set 1 (temurin-11) with skip bytebuffers:false
The hosted runner: GitHub Actions 378 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Integration Test Set 1 (temurin-21) with skip bytebuffers:true
The hosted runner: GitHub Actions 617 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Unit Test Set 2 (temurin-21) with skip bytebuffers:false
The hosted runner: GitHub Actions 652 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Integration Test Set 2 (temurin-21) with skip bytebuffers:true
The hosted runner: GitHub Actions 726 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Integration Test Set 1 (temurin-11) with skip bytebuffers:false
The hosted runner: GitHub Actions 757 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Unit Test Set 2 (temurin-11) with skip bytebuffers:false
The hosted runner: GitHub Actions 745 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Unit Test Set 1 (temurin-21) with skip bytebuffers:true
The hosted runner: GitHub Actions 801 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Pinot Integration Test Set 1 (temurin-21) with skip bytebuffers:false
Received request to deprovision: The request was cancelled by the remote provider.
Pinot Compatibility Regression Testing against release-1.2.0 on compatibility-verifier/sample-test-suite
Received request to deprovision: The request was cancelled by the remote provider.