Skip to content

fix: initialize separate logger for each module #1084

fix: initialize separate logger for each module

fix: initialize separate logger for each module #1084

Triggered via pull request August 29, 2025 09:08
Status Success
Total duration 7m 31s
Artifacts 2

build-test-release.yml

on: pull_request
Matrix: run-unit-tests
fossa-scan
50s
fossa-scan
compliance-copyrights
30s
compliance-copyrights
pre-commit
17s
pre-commit
semgrep  /  sast-scan
28s
semgrep / sast-scan
Matrix: test-splunk
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
test-unit 3.10
Process completed with exit code 1.
test-unit 3.9
Process completed with exit code 1.
test-unit 3.8
Process completed with exit code 1.
test-unit 3.11
Process completed with exit code 1.
test-unit 3.12
Process completed with exit code 1.
test-unit 3.13
Process completed with exit code 1.
test-unit 3.7
Process completed with exit code 1.
test-splunk (9.4.0, 6b4ebe426ca6, true, false)
Process completed with exit code 1.
test-splunk (9.2.4, c103a21bb11d, false, false)
Process completed with exit code 1.
test-splunk (9.3.2, d8bb32809498, false, false)
Process completed with exit code 1.
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:182673acdbcb0cb348343b968a9e5d6853624df1a614b586b4ec754912729ef7
semgrep_output.json Expired
688 Bytes
sha256:5e85b2e36f661fa26dfbac348c5ebdcd15ba1d03fb65d24a461d203ff7a35b80