docs(sweep): AbLegacy verified green — fixture-deployment gap, no code (#4) #449

2026-07-15T05:38:26-04:00

dohertj2 commented

2026-07-15 05:38:26 -04:00

Integration-sweep follow-up #4. AbLegacy 4F was a fixture-deployment gap, not a defect: the suite needs ab_server in PCCC mode (reuses the AbCip image, binds :44818) and none was deployed; the 4F-not-skip means a leftover CIP-mode container answered :44818 wrong. Deployed to ~/otopcua-ablegacy and ran each family with AB_LEGACY_COMPOSE_PROFILE set: slc500 2/2, micrologix 1/1, plc5 1/1. No code change; corrected the sweep record + added the recipe.

dohertj2 added 1 commit 2026-07-15 05:38:27 -04:00

docs(sweep): AbLegacy verified green — fixture-deployment gap, not a code defect (#4 )

v2-ci / build (pull_request) Successful in 4m26s

Details

v2-ci / unit-tests (pull_request) Failing after 3h11m47s

Details

f381b471f9

The sweep's AbLegacy 4F was a fixture-deployment gap, not a driver/test defect.
The suite needs ab_server in PCCC mode (--plc=SLC500|Micrologix|PLC/5), which
reuses the AbCip image (already on the host) and binds :44818. No PCCC container
was deployed, and the 4F-not-skip means :44818 was answering CIP (a leftover
AbCip container) so the PCCC reads returned Bad — same shared-port contamination
class as the Modbus false alarm.

Deployed the PCCC compose to ~/otopcua-ablegacy and ran each family with
AB_LEGACY_COMPOSE_PROFILE set to match the running container (required — without
it the [Theory] parametrises over all 3 families and 2 fail against a single-
family container): slc500 2/2, micrologix 1/1 (+1 skip), plc5 1/1 (+1 skip).
Skips are family-inapplicable file types. No code change.

Corrected the sweep record + added the AbLegacy bring-up + run recipe.
Integration-sweep follow-up #4.

dohertj2 merged commit 00d8422cef into master

2026-07-15 05:38:39 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#449