John Poole
65a3b73014
Some checks are pending
Tests / Detect Changes (push) Waiting to run
Tests / Unit Tests (push) Blocked by required conditions
Tests / Unit Tests-1 (push) Blocked by required conditions
Tests / Unit Tests-2 (push) Blocked by required conditions
Tests / Unit Tests-3 (push) Blocked by required conditions
Tests / Integration Tests (push) Blocked by required conditions
Tests / Integration Tests-1 (push) Blocked by required conditions
Tests / Integration Tests-2 (push) Blocked by required conditions
Tests / Integration Tests-3 (push) Blocked by required conditions
Tests / Installer Test (Fresh System) (push) Blocked by required conditions
Tests / Installer Test (Fresh System)-1 (push) Blocked by required conditions
Tests / Installer Test (Fresh System)-2 (push) Blocked by required conditions
Tests / Installer Test (Fresh System)-3 (push) Blocked by required conditions
Tests / Installer Test (Fresh System)-4 (push) Blocked by required conditions
Tests / Installer Test (Raspberry Pi OS - ARM) (push) Waiting to run
Tests / Installer Test (Raspberry Pi OS - ARM)-1 (push) Waiting to run
|
||
|---|---|---|
| .. | ||
| protocol_core | ||
| reports | ||
| scripts | ||
| sql | ||
| tests | ||
| .gitignore | ||
| ble_symbols_20260516_1429.txt | ||
| Codex_prompt_20250616_1449.md | ||
| Codex_response_20260616_1514.md | ||
| README.md | ||
| reticulum_info_20260516_1444.txt | ||
This directory concerns the migration to C++ the ble-reticulum project.
Test environment note
The project pytest configuration expects pytest-asyncio. 2 warning had issued, I had to rem the --disable-warnings flag in pytest.ini for the warnings to appear, when they appeared is became obvious that the absence of pytest-asyncio was creating the problem.
FIX: Install in the active virtual environment:
python3 -m pip install pytest-asyncio
Equivalence test:
cd /usr/local/src/ble-reticulum
python3 -m pytest migration/tests/test_fragmentation_cpp_equivalence.py -vv