Skip to content

Feature / Add fsspec implementation for GCP storage in the runtime #1188

Feature / Add fsspec implementation for GCP storage in the runtime

Feature / Add fsspec implementation for GCP storage in the runtime #1188

Triggered via pull request June 21, 2023 12:44
Status Failure
Total duration 6m 24s
Artifacts 1

integration.yml

on: pull_request
Matrix: int-metadb
Matrix: int-storage
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
end-to-end
Process completed with exit code 1.
int-metadb (MariaDB, mariadb:10.3, 3306, --health-cmd="mysqladmin ping" --health-interval=10s --h...
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
int-metadb (PostgreSQL, postgres:10-alpine, 5432, --health-cmd pg_isready --health-interval 10s -...
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
int-metadb (SQLServer, mcr.microsoft.com/mssql/server:2019-latest, 1433, -e "NO_DB_OPTIONS=not_us...
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
int-metadb (MySQL, mysql:8.0, 3306, --health-cmd="mysqladmin ping" --health-interval=10s --health...
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

Artifacts

Produced during runtime
Name Size
junit-test-results Expired
1010 KB