Skip to content

GH-4896 LMDB: Update benchmarks and improve performance (#4897) #866

GH-4896 LMDB: Update benchmarks and improve performance (#4897)

GH-4896 LMDB: Update benchmarks and improve performance (#4897) #866

Triggered via push February 5, 2024 08:49
Status Failure
Total duration 31m 32s
Artifacts
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 4 warnings
build (11)
java.lang.InterruptedException
build (11)
java.lang.InterruptedException
build (11)
Connection has been closed
build (11)
java.lang.InterruptedException
build (11)
java.lang.InterruptedException
build (21)
Resource not accessible by integration
build (21)
java.lang.InterruptedException
build (21)
java.lang.InterruptedException
build (21)
Connection has been closed
build (21)
java.lang.InterruptedException
build (21)
Connection has been closed
build (21)
Process completed with exit code 1.
build (11)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (21)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2, scacap/action-surefire-report@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/