Skip to content

chore(server): mark old raft configs as deprecated (#2661) #2

chore(server): mark old raft configs as deprecated (#2661)

chore(server): mark old raft configs as deprecated (#2661) #2

Triggered via push September 12, 2024 09:36
Status Success
Total duration 8m 23s
Artifacts

commons-ci.yml

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

Annotations

9 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)
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/