Skip to content

build(deps): bump actions/setup-python from 5 to 6 #1761

build(deps): bump actions/setup-python from 5 to 6

build(deps): bump actions/setup-python from 5 to 6 #1761

Triggered via pull request September 8, 2025 21:21
Status Success
Total duration 8m 31s
Artifacts

ci.yml

on: pull_request
Matrix: downstream_tests
Matrix: pytest
Fit to window
Zoom out
Zoom in

Annotations

55 warnings
Ruff
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
Pylint
modifying pylint run because we're on Python 3.13
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest without Numpy: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2358) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: .env/lib/python3.13/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x ubuntu-latest: /opt/hostedtoolcache/Python/3.13.7/x64/lib/python3.13/multiprocessing/popen_fork.py#L67
This process (pid=2572) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.10 ubuntu-latest: .env/lib/python3.10/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)
Pytest on Py3.12 ubuntu-latest: .env/lib/python3.12/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.12 ubuntu-latest: /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/multiprocessing/popen_fork.py#L66
This process (pid=2553) is multi-threaded, use of fork() may lead to deadlocks in the child.
Pytest on Py3.x macos-latest: .env/lib/python3.13/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)
Pytest on Py3.12 macos-latest: .env/lib/python3.12/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)
Pytest on Py3.10 macos-latest: .env/lib/python3.10/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)
Pytest on Pypypy3.10 ubuntu-latest: .env/lib/pypy3.10/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)
Tests for downstream project loopy: loopy/loopy/target/execution.py#L309
Unable to generate code to automatically find 'im_h' from 'img':
Tests for downstream project loopy: loopy/loopy/target/execution.py#L309
Unable to generate code to automatically find 'im_h' from 'img':
Tests for downstream project loopy: loopy/loopy/target/execution.py#L309
Unable to generate code to automatically find 'N' from 'x': division with remainder in linear solve for 'N'
Tests for downstream project loopy: loopy/loopy/target/execution.py#L309
Unable to generate code to automatically find 'N' from 'x': division with remainder in linear solve for 'N'
Tests for downstream project loopy: loopy/loopy/target/c/c_execution.py#L339
'GCCToolchain.copy' is deprecated. This is now a dataclass and should be used with the standard 'replace'.
Tests for downstream project loopy: loopy/loopy/target/c/c_execution.py#L322
'GCCToolchain.copy' is deprecated. This is now a dataclass and should be used with the standard 'replace'.
Tests for downstream project loopy: loopy/test/test_expression.py#L329
Using default C compiler because gcc-10 was not found. These tests may take a long time, because of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127.
Tests for downstream project loopy: loopy/loopy/target/c/c_execution.py#L339
'GCCToolchain.copy' is deprecated. This is now a dataclass and should be used with the standard 'replace'.
Tests for downstream project loopy: loopy/loopy/target/c/c_execution.py#L322
'GCCToolchain.copy' is deprecated. This is now a dataclass and should be used with the standard 'replace'.
Tests for downstream project loopy: loopy/test/test_expression.py#L329
Using default C compiler because gcc-10 was not found. These tests may take a long time, because of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Tests for downstream project pytato: pytato/pytato/target/loopy/__init__.py#L248
TranslationUnit.__call__ is uncached as of 2025, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
Pytest on Pypypy3.10 macos-latest: .env/lib/pypy3.10/site-packages/_pytest/config/__init__.py#L1291
assertions not in test modules or plugins will be ignored because assert statements are not executed by the underlying Python interpreter (are you using python -O?)