Skip to content
Unit Tests

Special log formatter for running tests #758

Sign in to view logs

Special log formatter for running tests

Special log formatter for running tests #758

Triggered via push January 17, 2024 15:10
@pwojcikdevpwojcikdev
pushed 3797261
logging-overhaul-9-develop
Status Failure
Total duration 44m 36s
Artifacts –

unit_tests.yml

on: push
Matrix: linux_test
Matrix: macos_test
Matrix: windows_test
Fit to window
Zoom out
Zoom in

Annotations

24 errors
Windows [rocksdb]
Process completed with exit code 1.
Windows [lmdb]
Process completed with exit code 1.
Linux [lmdb | gcc]
Process completed with exit code 134.
Linux [lmdb | gcc]
Process completed with exit code 134.
Linux [lmdb | gcc]
Process completed with exit code 134.
Linux [lmdb | gcc]
Process completed with exit code 1.
Linux [rocksdb | gcc]
Process completed with exit code 1.
Linux [rocksdb | gcc]
Process completed with exit code 134.
Linux [rocksdb | gcc]
Process completed with exit code 134.
Linux [rocksdb | gcc]
Process completed with exit code 134.
Linux [rocksdb | clang]
Process completed with exit code 134.
Linux [rocksdb | clang]
Process completed with exit code 134.
Linux [rocksdb | clang]
Process completed with exit code 1.
Linux [rocksdb | clang]
Process completed with exit code 134.
Linux [lmdb | clang]
Process completed with exit code 134.
Linux [lmdb | clang]
Process completed with exit code 134.
Linux [lmdb | clang]
Process completed with exit code 1.
Linux [lmdb | clang]
Process completed with exit code 134.
macOS [lmdb]
Process completed with exit code 1.
macOS [lmdb]
Process completed with exit code 134.
macOS [lmdb]
Process completed with exit code 134.
macOS [rocksdb]
Process completed with exit code 1.
macOS [rocksdb]
Process completed with exit code 134.
macOS [rocksdb]
Process completed with exit code 134.