Skip to content

fix: initialize separate logger for each module #1077

fix: initialize separate logger for each module

fix: initialize separate logger for each module #1077

Triggered via pull request August 21, 2025 11:19
Status Success
Total duration 5m 59s
Artifacts 2

build-test-release.yml

on: pull_request
Matrix: run-unit-tests
fossa-scan
3m 37s
fossa-scan
compliance-copyrights
27s
compliance-copyrights
pre-commit
40s
pre-commit
semgrep  /  sast-scan
22s
semgrep / sast-scan
Matrix: test-splunk
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
test-unit 3.9
Process completed with exit code 2.
test-unit 3.10
Process completed with exit code 2.
test-unit 3.11
Process completed with exit code 2.
test-unit 3.8
Process completed with exit code 2.
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:9d856b94772fbb4d7120e05954d162b54c9ef4d1dd076a0f8f8c3e3e3e18cb84
semgrep_output.json Expired
746 Bytes
sha256:8be557ab352c7ea261c2c61b71c324ce367cdd103c0941b0e0b0b64f8b7c3aeb