Skip to content

refactor(interactive): Introduce call_proc as a new physical operator and implement it #5435

refactor(interactive): Introduce call_proc as a new physical operator and implement it

refactor(interactive): Introduce call_proc as a new physical operator and implement it #5435

Triggered via pull request October 21, 2024 12:20
Status Failure
Total duration 1h 12m 34s
Artifacts 4

k8s-ci.yml

on: pull_request
build-gie-experimental
0s
build-gie-experimental
build-analytical-java
0s
build-analytical-java
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
build-gie-experimental
The self-hosted runner: graphscope-runners-manylinux2014-q742h-4wjrn lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
k8s-test
Process completed with exit code 1.
changes
'base' input parameter is ignored when action is triggered by pull request event
k8s-test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
k8s-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
analytical Expired
9.86 MB
interactive Expired
146 MB
k8s-test-logs
23.2 MB
learning Expired
43.2 MB