Fixes #123 #181
Triggered via pull request
September 17, 2024 12:48
edgararuiz
Status
Failure
Total duration
9m 18s
Artifacts
–
Annotations
10 errors and 1 warning
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
Connection with Databricks failed: "Failed to perform HTTP request. Caused by error in `curl::curl_fetch_memory()`: ! Failed to connect to localhost port 443 after 0 ms: Connection refused"
|
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
Connection with Databricks failed: "HTTP 400 Bad Request."
|
|
PySpark 3.5
There were failures
|
|
PySpark 3.5
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|