Skip to content

feat(server): support in-heap memory JVM monitor (#2650) #4

feat(server): support in-heap memory JVM monitor (#2650)

feat(server): support in-heap memory JVM monitor (#2650) #4

Triggered via push October 17, 2024 11:55
Status Success
Total duration 2m 45s
Artifacts

commons-ci.yml

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

Annotations

7 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)
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/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/