You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running pytest on a raspberry PI after creating the python-bindings, using all the threads causes the workers to crash and for some tests to fail.
Problem to solve
Change the number of threads to 1 when running tests on raspberry pi
Proposals
Update the frontends/concrete-python/Makefile and change pytest-default to detect if it is running on a raspberry pi. Example of update to pytest-default could be:
pytest-default:
export LD_PRELOAD=$(RUNTIME_LIBRARY)
export PYTHONPATH=$(BINDINGS_DIRECTORY)
@# Check if running on Raspberry Pi
@if grep -q 'Raspberry Pi' /proc/cpuinfo; then \
echo "Running on Raspberry Pi, setting pytest threads to 1."; \
PYTEST_THREADS=1; \
else \
PYTEST_THREADS=auto; \
fi; \
pytest tests -svv -n $$PYTEST_THREADS \
--cov=concrete.fhe \
--cov-fail-under=95 \
--cov-report=term-missing:skip-covered \
--key-cache "${KEY_CACHE_DIRECTORY}" \
-m "${PYTEST_MARKERS}"
The text was updated successfully, but these errors were encountered:
Summary
When running pytest on a raspberry PI after creating the python-bindings, using all the threads causes the workers to crash and for some tests to fail.
Problem to solve
Change the number of threads to 1 when running tests on raspberry pi
Proposals
Update the frontends/concrete-python/Makefile and change pytest-default to detect if it is running on a raspberry pi. Example of update to pytest-default could be:
The text was updated successfully, but these errors were encountered: