Skip to content

fix: initialize separate logger for each module #1076

fix: initialize separate logger for each module

fix: initialize separate logger for each module #1076

Triggered via pull request August 21, 2025 08:15
Status Failure
Total duration 3m 55s
Artifacts 2

build-test-release.yml

on: pull_request
Matrix: run-unit-tests
fossa-scan
35s
fossa-scan
compliance-copyrights
29s
compliance-copyrights
pre-commit
37s
pre-commit
semgrep  /  sast-scan
29s
semgrep / sast-scan
Matrix: test-splunk
publish
0s
publish
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 1 warning
test-unit 3.11
Process completed with exit code 2.
test-unit 3.9
Process completed with exit code 2.
test-unit 3.8
Process completed with exit code 2.
test-unit 3.10
Process completed with exit code 2.
pre-commit
Process completed with exit code 1.
test-unit 3.12
Process completed with exit code 2.
test-unit 3.13
Process completed with exit code 2.
test-unit 3.7
Process completed with exit code 2.
test-splunk (9.4.0, 6b4ebe426ca6, true, false)
Process completed with exit code 2.
test-splunk (9.2.4, c103a21bb11d, false, false)
Process completed with exit code 2.
test-splunk (9.3.2, d8bb32809498, false, false)
Process completed with exit code 2.
compliance-copyrights
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.

Artifacts

Produced during runtime
Name Size Digest
THIRDPARTY Expired
8.14 KB
sha256:bebc11b29517b5c03bb8ee994e4ffafcc226d28dda0941059a72e77ef6dfdc9a
semgrep_output.json Expired
741 Bytes
sha256:bcff8f8fc8449691379430298b967320389cc2849ef9e4da7fe296b060d16068