fix: do not warn on pipx, venv, setuptools installations + fix doxygen warning + feat: support all brew install options + fix: require python 3.8.0 for cpplint #1597
aminyaAnnotations
2 errors, 67 warnings, and 40 notices
|
Test-ubuntu-20.04
Failed to install nala via installer: Error: Command failed with exit code 100: sudo 'bash' '/tmp/install-nala.sh'
|
|
Test-windows-2019
Process completed with exit code 1.
|
|
Build (ubuntu-22.04)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build-Executable-ubuntu-24.04
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build-Executable-macos-14
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build-Executable-macos-13
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build-Executable-windows-2022
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Docker-setup-cpp-ubuntu-mingw
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Docker-setup-cpp-fedora-llvm
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Docker-setup-cpp-ubuntu-llvm
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-macos-14
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-macos-14
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-macos-14
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-14
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-macos-14
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-14
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-14
graphviz 12.1.2 is already installed and up-to-date.
To reinstall 12.1.2, run:
brew reinstall graphviz
|
|
Test-macos-14
bazelisk 1.22.1 is already installed and up-to-date.
To reinstall 1.22.1, run:
brew reinstall bazelisk
|
|
Test-macos-14
p7zip 17.05 is already installed and up-to-date.
To reinstall 17.05, run:
brew reinstall p7zip
|
|
Test-ubuntu-24.04
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-ubuntu-24.04
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-ubuntu-24.04
‘CURLFORM_COPYNAME’ is deprecated: since 7.56.0. Use curl_mime_name() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘CURLFORM_FILE’ is deprecated: since 7.56.0. Use curl_mime_filedata() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘CURLFORMcode curl_formadd(curl_httppost**, curl_httppost**, ...)’ is deprecated: since 7.56.0. Use curl_mime_init() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘CURLOPT_HTTPPOST’ is deprecated: since 7.56.0. Use CURLOPT_MIMEPOST [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘void curl_formfree(curl_httppost*)’ is deprecated: since 7.56.0. Use curl_mime_free() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘CURLFORM_COPYNAME’ is deprecated: since 7.56.0. Use curl_mime_name() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘CURLFORM_FILE’ is deprecated: since 7.56.0. Use curl_mime_filedata() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘CURLFORMcode curl_formadd(curl_httppost**, curl_httppost**, ...)’ is deprecated: since 7.56.0. Use curl_mime_init() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘CURLOPT_HTTPPOST’ is deprecated: since 7.56.0. Use CURLOPT_MIMEPOST [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
‘void curl_formfree(curl_httppost*)’ is deprecated: since 7.56.0. Use curl_mime_free() [-Wdeprecated-declarations]
|
|
Test-ubuntu-24.04
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-ubuntu-22.04
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-ubuntu-22.04
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-ubuntu-22.04
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-ubuntu-20.04
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-ubuntu-20.04
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-ubuntu-20.04
setup-cpp was called without any arguments. Nothing to do.
|
|
Docker-setup-cpp-arch-llvm
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-macos-13
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-macos-13
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-macos-13
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-13
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-13
graphviz 12.1.2 is already installed and up-to-date.
To reinstall 12.1.2, run:
brew reinstall graphviz
|
|
Test-macos-13
bazelisk 1.22.1 is already installed and up-to-date.
To reinstall 1.22.1, run:
brew reinstall bazelisk
|
|
Test-macos-13
p7zip 17.05 is already installed and up-to-date.
To reinstall 17.05, run:
brew reinstall p7zip
|
|
Test-macos-13
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-macos-13
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-12
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-macos-12
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-12
doxygen 1.12.0 is already installed and up-to-date.
To reinstall 1.12.0, run:
brew reinstall doxygen
|
|
Test-macos-12
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
Test-macos-12
graphviz 12.1.1 is already installed and up-to-date.
To reinstall 12.1.1, run:
brew reinstall graphviz
|
|
Test-macos-12
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
Test-macos-12
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
Test-macos-12
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
Test-macos-12
bazelisk 1.21.0 is already installed and up-to-date.
To reinstall 1.21.0, run:
brew reinstall bazelisk
|
|
Test-macos-12
p7zip 17.05 is already installed and up-to-date.
To reinstall 17.05, run:
brew reinstall p7zip
|
|
Test-macos-12
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
Test-macos-12
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-macos-12
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-macos-12
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-macos-12
gcc 14.2.0 is already installed and up-to-date.
To reinstall 14.2.0, run:
brew reinstall gcc
|
|
Test-windows-2022
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-windows-2022
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-windows-2022
setup-cpp was called without any arguments. Nothing to do.
|
|
Test-windows-2019
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Test-windows-2019
Error: Microsoft Visual Studio not found
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "dist", "exe".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-14
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-13
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-macos-12
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2022
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
|
Test-windows-2019
Failed to install venv: Error: Failed to install venv as it was not found via pip or the system package manager. Ignoring...
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
aminya~setup-cpp~AFHT6L.dockerbuild
|
17.2 KB |
|
|
aminya~setup-cpp~DU0QX3.dockerbuild
|
17.5 KB |
|
|
aminya~setup-cpp~J4MM6C.dockerbuild
|
18.7 KB |
|
|
aminya~setup-cpp~K6IH2L.dockerbuild
|
102 KB |
|
|
aminya~setup-cpp~P1B4QX.dockerbuild
|
108 KB |
|
|
aminya~setup-cpp~SRF3DI.dockerbuild
|
46 KB |
|
|
aminya~setup-cpp~X0FPJD.dockerbuild
|
17.4 KB |
|
|
aminya~setup-cpp~ZAHBJD.dockerbuild
|
128 KB |
|
|
dist
Expired
|
6.47 MB |
|
|
exe
Expired
|
158 MB |
|