Skip to content

Improve MemoryMonitor implementation. #25

Improve MemoryMonitor implementation.

Improve MemoryMonitor implementation. #25

Triggered via push February 28, 2025 09:17
Status Failure
Total duration 22s
Artifacts

test.yaml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 2 warnings
3.1 on ubuntu
Process completed with exit code 1.
3.4 on macos
The job was canceled because "ubuntu_3_1_false" failed.
3.3 on macos
The job was canceled because "ubuntu_3_1_false" failed.
3.1 on macos
The job was canceled because "ubuntu_3_1_false" failed.
3.2 on macos
The job was canceled because "ubuntu_3_1_false" failed.
3.4 on ubuntu
The job was canceled because "ubuntu_3_1_false" failed.
3.4 on ubuntu
Process completed with exit code 1.
truffleruby on ubuntu
The job was canceled because "ubuntu_3_1_false" failed.
truffleruby on ubuntu
The operation was canceled.
3.2 on ubuntu
The job was canceled because "ubuntu_3_1_false" failed.
3.2 on ubuntu
Process completed with exit code 1.
jruby on ubuntu
The job was canceled because "ubuntu_3_1_false" failed.
jruby on ubuntu
The operation was canceled.
3.3 on ubuntu
The job was canceled because "ubuntu_3_1_false" failed.
3.3 on ubuntu
The operation was canceled.
head on ubuntu
The job was canceled because "ubuntu_3_1_false" failed.
head on ubuntu
The operation was canceled.
3.2 on ubuntu
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
3.3 on ubuntu
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists