Skip to content
Back to pull request #2649

feat(server): support MemoryManagement for graph query framework #228

Sign in to view logs

feat(server): support MemoryManagement for graph query framework

feat(server): support MemoryManagement for graph query framework #228

Triggered via pull request November 4, 2024 11:50
@PengznaPengzna
synchronize #2649
Pengzna:memory/management
Status Success
Total duration 23m 33s
Artifacts –

commons-ci.yml

on: pull_request
Matrix: build-commons
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
expected:<Fri Jan 02 15:54:17 UTC 1> but was:<Sat Jan 03 00:00:00 UTC 1>
build-commons (11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v3, actions/cache@v3, actions/checkout@v3, codecov/codecov-action@v3.0.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/