Fix memory leak with pMsg #399
develop.yml
on: push
Check if build should be stopped
4s
git
/
block-fixup
Matrix: build / Flatpak
Matrix: build / build
Matrix: checks / build-checks
Ready to merge
0s
Annotations
28 errors and 12 warnings
|
build / Windows 11 VS2026 ARM64
Process completed with exit code 1.
|
|
build / Windows 11 VS2026 ARM64:
src/mixxxmainwindow.cpp#L1313
'pMsg': undeclared identifier
|
|
build / Windows 11 VS2026 ARM64:
src/mixxxmainwindow.cpp#L1312
'pMsg': undeclared identifier
|
|
build / macOS 15 x64
Process completed with exit code 1.
|
|
build / macOS 15 x64:
src/mixxxmainwindow.cpp#L1313
use of undeclared identifier 'pMsg'
|
|
build / macOS 15 x64:
src/mixxxmainwindow.cpp#L1312
use of undeclared identifier 'pMsg'
|
|
build / Windows Server 2025 VS2026 x64
Process completed with exit code 1.
|
|
build / Windows Server 2025 VS2026 x64:
src/mixxxmainwindow.cpp#L1313
'pMsg': undeclared identifier
|
|
build / Windows Server 2025 VS2026 x64:
src/mixxxmainwindow.cpp#L1312
'pMsg': undeclared identifier
|
|
build / macOS 15 arm64
Process completed with exit code 1.
|
|
build / macOS 15 arm64:
src/mixxxmainwindow.cpp#L1313
use of undeclared identifier 'pMsg'
|
|
build / macOS 15 arm64:
src/mixxxmainwindow.cpp#L1312
use of undeclared identifier 'pMsg'
|
|
build / Flatpak (aarch64, ubuntu-24.04-arm)
Build failed: Error: The process '/app/bin/xvfb-run' failed with exit code 1
|
|
build / Flatpak (x86_64, ubuntu-24.04)
The strategy configuration was canceled because "build.build-flatpak.aarch64_ubuntu-24_04-arm" failed
|
|
build / Flatpak (x86_64, ubuntu-24.04)
The operation was canceled.
|
|
build / Android 15 arm64
Process completed with exit code 2.
|
|
build / Android 15 arm64:
src/mixxxmainwindow.cpp#L1313
use of undeclared identifier 'pMsg'
|
|
build / Android 15 arm64:
src/mixxxmainwindow.cpp#L1312
use of undeclared identifier 'pMsg'
|
|
checks / coverage
Process completed with exit code 2.
|
|
checks / coverage:
src/mixxxmainwindow.cpp#L1312
‘pMsg’ was not declared in this scope
|
|
checks / clang-tidy
The strategy configuration was canceled because "checks.build-checks.coverage" failed
|
|
checks / clang-tidy
The operation was canceled.
|
|
checks / clazy
The strategy configuration was canceled because "checks.build-checks.coverage" failed
|
|
checks / clazy
The operation was canceled.
|
|
checks / clazy:
src/mixxxmainwindow.cpp#L1313
use of undeclared identifier 'pMsg'
|
|
checks / clazy:
src/mixxxmainwindow.cpp#L1312
use of undeclared identifier 'pMsg'
|
|
build / Ubuntu 24.04
Process completed with exit code 2.
|
|
build / Ubuntu 24.04:
src/mixxxmainwindow.cpp#L1312
‘pMsg’ was not declared in this scope
|
|
pre-commit / Detecting code style issues
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Windows 11 VS2026 ARM64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/msvc-problem-matcher@0.3.0, ilammy/msvc-dev-cmd@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / macOS 15 x64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/gcc-problem-matcher@0.3.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / macOS 15 x64
The following taps are not trusted:
aws/tap
azure/bicep
Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set.
This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first.
Enable trust checks now with:
export HOMEBREW_REQUIRE_TAP_TRUST=1
Trust specific formulae, casks or commands with:
brew trust --formula <user>/<tap>/<formula>
brew trust --cask <user>/<tap>/<cask>
brew trust --command <user>/<tap>/<command>
or trust installed formulae from these taps with:
brew trust --formula azure/bicep/bicep
You can trust all formulae, casks and commands from these taps with:
brew trust aws/tap azure/bicep
Prefer trusting only the specific formulae, casks or commands you need.
Untap them with:
brew untap aws/tap azure/bicep
To keep allowing them by default during the transition:
export HOMEBREW_NO_REQUIRE_TAP_TRUST=1
This is not recommended and will be removed in a later release.
|
|
build / Windows Server 2025 VS2026 x64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/msvc-problem-matcher@0.3.0, ilammy/msvc-dev-cmd@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / macOS 15 arm64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/gcc-problem-matcher@0.3.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / macOS 15 arm64
The following taps are not trusted:
aws/tap
azure/bicep
Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set.
This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first.
Enable trust checks now with:
export HOMEBREW_REQUIRE_TAP_TRUST=1
Trust specific formulae, casks or commands with:
brew trust --formula <user>/<tap>/<formula>
brew trust --cask <user>/<tap>/<cask>
brew trust --command <user>/<tap>/<command>
or trust installed formulae from these taps with:
brew trust --formula azure/bicep/bicep
You can trust all formulae, casks and commands from these taps with:
brew trust aws/tap azure/bicep
Prefer trusting only the specific formulae, casks or commands you need.
Untap them with:
brew untap aws/tap azure/bicep
To keep allowing them by default during the transition:
export HOMEBREW_NO_REQUIRE_TAP_TRUST=1
This is not recommended and will be removed in a later release.
|
|
build / Android 15 arm64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/gcc-problem-matcher@0.3.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
checks / coverage
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/gcc-problem-matcher@0.3.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
checks / clang-tidy
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/gcc-problem-matcher@0.3.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
checks / clazy
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/gcc-problem-matcher@0.3.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Ubuntu 24.04
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ammaraskar/gcc-problem-matcher@0.3.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|