Leica M Monochrom normalization #2174
kmilosCI.yml
on: pull_request
cache-rpuu
/
Cache RPU masterset
18s
Matrix: linux-fast
Matrix: macOS-fast
Matrix: windows-msys2-fast
Matrix: linux-coverage
Matrix: linux-legacy
Matrix: linux-ossfuzz
Matrix: linux-sonarcloud-static-analysis
Waiting for pending jobs
Matrix: linux-static-analysis
Matrix: macOS-coverage
Waiting for pending jobs
Matrix: macOS-legacy
Waiting for pending jobs
Matrix: windows-msys2-coverage
codecov
/
Upload code coverage reports to codecov
Annotations
3 errors and 12 warnings
|
macOS-fast (macos-15-intel, XCode, 26.3, 15.5, cc, c++, Release) / XCode.26.3.targeting.OSX.15.5.Release
The action 'Remove unneeded brew formulas/casks' has timed out after 3 minutes.
|
|
|
|
linux-coverage (linux, debian:forky-slim, GNU, 15, gcc-15, g++-15, gcov-15, Coverage) / ubuntu-latest // debian:forky-slim.GNU15.Coverage
The action 'Test (integration)' has timed out after 31 minutes.
|
|
windows-msys2-fast (windows-latest, CLANG64, x86_64, LLVM, clang, clang++, ReleaseWithAsserts) / windows-latest.CLANG64.LLVM.ReleaseWithAsserts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-fast (windows-latest, CLANG64, x86_64, LLVM, clang, clang++, Release) / windows-latest.CLANG64.LLVM.Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-fast (windows-latest, MINGW64, x86_64, GNU, gcc, g++, Release) / windows-latest.MINGW64.GNU.Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-fast (windows-latest, MINGW32, i686, GNU, gcc, g++, Release) / windows-latest.MINGW32.GNU.Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-fast (windows-latest, MINGW64, x86_64, GNU, gcc, g++, ReleaseWithAsserts) / windows-latest.MINGW64.GNU.ReleaseWithAsserts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-fast (windows-latest, UCRT64, x86_64, GNU, gcc, g++, ReleaseWithAsserts) / windows-latest.UCRT64.GNU.ReleaseWithAsserts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-fast (windows-latest, MINGW32, i686, GNU, gcc, g++, ReleaseWithAsserts) / windows-latest.MINGW32.GNU.ReleaseWithAsserts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-fast (windows-latest, UCRT64, x86_64, GNU, gcc, g++, Release) / windows-latest.UCRT64.GNU.Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-msys2-coverage (windows-latest, UCRT64, x86_64, GNU, gcc, g++, Coverage) / windows-latest.UCRT64.GNU.Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: msys2/setup-msys2@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux-static-analysis (linux, debian:forky-slim, LLVM, 21, clang-21, clang++-21, CodeQLAnalysis) / ubuntu-latest // debian:forky-slim.LLVM21.CodeQLAnalysis
Cannot create diff range extension pack for diff-informed queries; reverting to performing full analysis.
|
|
linux-static-analysis (linux, debian:forky-slim, LLVM, 21, clang-21, clang++-21, CodeQLAnalysis) / ubuntu-latest // debian:forky-slim.LLVM21.CodeQLAnalysis
Error retrieving diff develop...darktable-org:kmilos-patch-2: Not Found - https://docs.github.com/rest/commits/commits#compare-two-commits
|
|
linux-static-analysis (linux, debian:forky-slim, LLVM, 21, clang-21, clang++-21, CodeQLAnalysis) / ubuntu-latest // debian:forky-slim.LLVM21.CodeQLAnalysis
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses.
To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
codechecker_ctu_report
|
369 KB |
sha256:c97e7b82c5eb3c640f28be1ace0d5ca72e18ee98d6377e7e5e2773bdd8fe5ae7
|
|