Skip to content
ci

Bumped python version number #207

Sign in to view logs

Bumped python version number

Bumped python version number #207

Triggered via push February 25, 2025 23:34
@scharlton2scharlton2
pushed 2f93611
master
Status Success
Total duration 1h 12m 24s
Artifacts 4

ci.yml

on: push
init
3s
init
log-the-inputs
0s
log-the-inputs
Matrix: valgrind
make distcheck
4m 51s
make distcheck
display results
0s
display results
Matrix: autotools
Matrix: cmake-mpi
Matrix: cmake
deploy_pages
10s
deploy_pages
https://usgs-coupled.github.io/phreeqcrm/
Fit to window
Zoom out
Zoom in

Annotations

34 warnings
macos-13 shared=OFF yaml=OFF type=Debug
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
ubuntu-20.04 shared=OFF yaml=OFF type=Debug
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
macos-13 shared=OFF yaml=OFF type=Release
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
macos-13 shared=ON yaml=OFF type=Debug
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
ubuntu-20.04 shared=OFF yaml=OFF type=Release
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
macos-13 shared=ON yaml=OFF type=Release
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
macos-13 shared=OFF yaml=ON type=Debug
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
ubuntu-20.04 shared=OFF yaml=ON type=Debug
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
ubuntu-20.04 shared=ON yaml=OFF type=Debug
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
macos-13 shared=ON yaml=ON type=Debug
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
macos-13 shared=OFF yaml=ON type=Release
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
ubuntu-20.04 shared=ON yaml=OFF type=Release
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
ubuntu-20.04 shared=OFF yaml=ON type=Release
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
macos-13 shared=ON yaml=ON type=Release
gcc@12 12.4.0 is already installed and up-to-date. To reinstall 12.4.0, run: brew reinstall gcc@12
ubuntu-20.04 shared=ON yaml=ON type=Debug
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
ubuntu-20.04 shared=ON yaml=ON type=Release
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
windows-2019 shared=OFF yaml=OFF type=Debug
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2019 shared=OFF yaml=OFF type=Debug
Cache save failed.
windows-2022 shared=OFF yaml=OFF type=Debug
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2022 shared=OFF yaml=OFF type=Debug
Cache save failed.
windows-2022 shared=OFF yaml=OFF type=Release
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2022 shared=OFF yaml=OFF type=Release
Cache save failed.
windows-2019 shared=ON yaml=OFF type=Debug
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2019 shared=ON yaml=OFF type=Debug
Cache save failed.
windows-2019 shared=OFF yaml=ON type=Release
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2019 shared=OFF yaml=ON type=Release
Cache save failed.
windows-2019 shared=ON yaml=OFF type=Release
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2019 shared=ON yaml=OFF type=Release
Cache save failed.
windows-2019 shared=OFF yaml=ON type=Debug
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2019 shared=OFF yaml=ON type=Debug
Cache save failed.
windows-2022 shared=OFF yaml=ON type=Debug
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2022 shared=OFF yaml=ON type=Debug
Cache save failed.
windows-2019 shared=ON yaml=ON type=Debug
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
windows-2019 shared=ON yaml=ON type=Debug
Cache save failed.

Artifacts

Produced during runtime
Name Size
github-pages Expired
1.09 MB
readme
5.31 KB
tarball
8.27 MB
zip
8.57 MB