Skip to content

CI-037 - Expanded Live UI and E2E Weak-Path Stress Gate

Summary

Make the weak live paths explicit in the release proof instead of relying on separate focused runs. The new release-expanded aggregate profile is a bounded gate for adversity, UI, live search/download, shutdown/recovery, and aMuTorrent smoke coverage.

Acceptance

  • [x] live-e2e --profile release-expanded is a supported aggregate profile.
  • [x] The profile includes Preferences, Shared Files, shared-hash, Search UI, shared-directories REST, REST API, cold-start telemetry, local dump/crash smoke, and aMuTorrent browser smoke.
  • [x] The REST child receives 50 server searches, 50 Kad searches, and 100 required paused live download triggers.
  • [x] Success is defined as accepted trigger requests with materialized queue rows; completed downloads are not required.
  • [x] Aggregate reports include a weak-path matrix covering adversity, queued-download, UI, and integration targets.
  • [x] A current-head release-expanded live run is recorded before final packaging.

Evidence

  • Build-tests commit 04f46be adds the aggregate release-expanded profile and report matrix.
  • Build orchestration commit 617cc54 exposes the new profile through python -m emule_workspace test live-e2e.
  • Targeted Python checks passed:
  • python -m pytest tests\python\test_live_e2e_suite.py -q
  • python -m pytest tests\test_live_e2e_options.py tests\test_cli.py -q
  • 2026-05-16 current-head live run:
  • command: python -m emule_workspace test live-e2e --profile release-expanded --fail-fast --live-wire-inputs-file repos\emulebb-build-tests\live-wire-inputs.local.json
  • aggregate report: repos\emulebb-build-tests\reports\live-e2e-suite\20260516-213444-eMule-main-release\result.json
  • aggregate status: passed
  • required live download triggers: 100/100
  • passed children: preference-ui, shared-files-ui, search-ui-live, shared-hash-ui, shared-directories-rest, rest-api, local-dumps-crash-smoke, amutorrent-browser-smoke
  • inconclusive child: rest-cold-start-dump-stress, because the live network exposed 40/150 safe active-download candidates during its extra cold-start candidate search; this did not affect the REST API 100/100 queued-trigger gate.