dohertj2/lmxopcua
1
0
Fork 0
Code Issues 43 Pull Requests Actions Packages Projects Releases Wiki Activity

CI: add a fixture-backed integration leg and a guarded E2E workflow #757

New Issue
Open
opened 2026-11-06 15:27:09 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:27:09 -05:00
Owner
Copy Link
Copy Source

The archreview round-2 STATUS recorded two open CI follow-ups that no issue tracks. #606 closed the rest of the engineering-system work.

  • (b) A fixture-backed integration leg, for example an opc-plc services: block with its own MIN_EXECUTED, covering what the offline unit leg cannot. Today .github/workflows/v2-ci.yml runs unit tests only.
  • (a) When a runner-reachable fleet and real tests/Server/…E2ETests exist, add an E2E workflow with a zero-match guard that fails if Category=E2E matches nothing. The old v2-e2e.yml was a silent no-op and was deleted.
  • Verify still open: the 2026-07-15 integration sweep recorded Host integration at 105/117, with 7 heavy E2E tests timing out under amd64-emulated SQL (OPEN). Re-run it and either fix the timeouts or document them.

Source: archreview/plans/STATUS.md:163-166; archreview/plans/INTEGRATION-SWEEP-STATUS.md:24. Related: #606, #723.

The archreview round-2 STATUS recorded two open CI follow-ups that no issue tracks. #606 closed the rest of the engineering-system work. - (b) A **fixture-backed integration leg**, for example an opc-plc `services:` block with its own `MIN_EXECUTED`, covering what the offline unit leg cannot. Today `.github/workflows/v2-ci.yml` runs unit tests only. - (a) When a runner-reachable fleet and real `tests/Server/…E2ETests` exist, add an E2E workflow **with a zero-match guard** that fails if `Category=E2E` matches nothing. The old `v2-e2e.yml` was a silent no-op and was deleted. - Verify still open: the 2026-07-15 integration sweep recorded Host integration at 105/117, with 7 heavy E2E tests timing out under amd64-emulated SQL (OPEN). Re-run it and either fix the timeouts or document them. Source: archreview/plans/STATUS.md:163-166; archreview/plans/INTEGRATION-SWEEP-STATUS.md:24. Related: #606, #723.
dohertj2 added the priority:p3migratedtype:infra labels 2026-11-06 15:28:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 blocked
Blocked by dependency or external hold
 cross-driver
queue management
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 driver/abcip
queue management
 driver/ablegacy
queue management
 driver/focas
queue management
 driver/mqtt
MQTT / Sparkplug B broker-subscribe driver
 driver/opcuaclient
queue management
 driver/s7
queue management
 driver/twincat
queue management
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label migrated priority:p3 type:infra
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#757
Delete Branch "%!s()"

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?