Skip to content
core

[ZEPPELIN-6358] Add E2E tests about /#/notebook/:noteid for New UI #5400

Sign in to view logs

[ZEPPELIN-6358] Add E2E tests about /#/notebook/:noteid for New UI

[ZEPPELIN-6358] Add E2E tests about /#/notebook/:noteid for New UI #5400

Triggered via pull request December 19, 2025 11:53
@dididydididy
synchronize #5101
dididy:e2e/notebook
Status Failure
Total duration 40m 21s
Artifacts –

core.yml

on: pull_request
livy-0-8-with-spark-3-2-under-python39
2m 54s
livy-0-8-with-spark-3-2-under-python39
Matrix: core-modules
Matrix: default-build
Matrix: flink-test-and-flink-integration-test
Matrix: interpreter-test-jupyter-python-rlang
Matrix: interpreter-test-non-core
Matrix: spark-integration-test
Matrix: spark-test
Matrix: windows-build
Matrix: zeppelin-integration-test
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
livy-0-8-with-spark-3-2-under-python39
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
interpreter-test-non-core (11)
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
spark-test (3.9, 11)
Process completed with exit code 1.
zeppelin-integration-test (11)
Process completed with exit code 1.
core-modules (11)
Process completed with exit code 1.
spark-test (3.9, 17)
0
livy-0-8-with-spark-3-2-under-python39
CondaHTTPError: HTTP 502 Bad Gateway for url <https://conda.anaconda.org/conda-forge/linux-64/repodata.json> Elapsed: 00:00.149044 CF-RAY: 9b06b6b6fb30cc8b-SJC A remote server error occurred when trying to retrieve this URL. A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to fulfill a valid request. The problem may be spurious, and will resolve itself if you try your request again. If the problem persists, consider notifying the maintainer of the remote server.
interpreter-test-non-core (11)
CondaHTTPError: HTTP 502 Bad Gateway for url <https://conda.anaconda.org/conda-forge/noarch/repodata.json> Elapsed: 00:32.771939 CF-RAY: 9b06b7465c32b341-SJC A remote server error occurred when trying to retrieve this URL. A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to fulfill a valid request. The problem may be spurious, and will resolve itself if you try your request again. If the problem persists, consider notifying the maintainer of the remote server.