Skip to content

fix: initialize separate logger for each module #1079

fix: initialize separate logger for each module

fix: initialize separate logger for each module #1079

Triggered via pull request August 22, 2025 07:55
Status Success
Total duration 6m 49s
Artifacts 2

build-test-release.yml

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

Annotations

10 errors and 1 warning
test-unit 3.11
Process completed with exit code 1.
test-unit 3.9
Process completed with exit code 1.
test-unit 3.10
Process completed with exit code 1.
test-unit 3.8
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-splunk (9.4.0, 6b4ebe426ca6, true, false)
Process completed with exit code 2.
test-unit 3.7
Process completed with exit code 1.
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:8b65c056e49e6e90f97ccd9e8cff5eebd1c678729f444cb127bffb6f7841bc2b
semgrep_output.json Expired
756 Bytes
sha256:2493df9fe65c39ff7fda7af3abd7db231d1f951e8ba4634ba1419123e9d10c39