docs(modbus-tests): sweep #2 was a fixture-cycling false alarm (all profiles green) #448
Reference in New Issue
Block a user
Delete Branch "fix/modbus-sweep-false-alarm"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Integration-sweep follow-up #2. The Modbus non-standard 8F/5F/3F/8F was NOT pymodbus drift (image runs the pinned 3.13.0) and NOT an OtOpcUa regression — it was a fixture-cycling artifact: profile-gated compose services share :5020 and 'docker compose down' (no --profile) doesn't stop the running one, so later profile runs hit the stale sim (proven: 'mitsubishi' served DL205's 0xCAFE). Bringing each up cleanly: dl205 16/16, mitsubishi 13/13, s7_1500 10/10, exception_injection 17/17. No code change — documented the gotcha + reliable-cycle recipe in Docker/README.md and corrected the sweep record.