Skip to content

aMuTorrent browser smoke ignores generated harness port

Summary

The dedicated aMuTorrent browser smoke can fail before browser execution because aMuTorrent serves the port persisted in repos\amutorrent\server\data\config.json instead of the generated PORT provided by the live harness.

Evidence

  • Command: python -m emule_workspace test live-e2e --config Release --platform x64 --suite amutorrent-browser-smoke --skip-live-seed-refresh
  • Artifact: EMULE_WORKSPACE_ROOT\repos\emulebb-build-tests\reports\amutorrent-browser-smoke\20260510-225224-eMule-main-release
  • eMule REST readiness and network readiness passed.
  • Harness waited on http://127.0.0.1:55939/api/config/status.
  • aMuTorrent log reported it was running on http://localhost:57415.

Acceptance Criteria

  • [x] The browser smoke launches aMuTorrent on the generated harness port or reliably discovers the actual bound port before readiness checks.
  • [x] The harness keeps aMuTorrent state isolated from persistent repos\amutorrent\server\data config between live runs.
  • [x] The dedicated aMuTorrent browser smoke passes on current beta 0.7.3 app main.

Validation

  • 2026-05-13: test commit b7477a3 added a regression guard that the browser smoke passes PORT and AMUTORRENT_DATA_DIR and does not use the persistent repos\amutorrent\server\data directory.
  • 2026-05-13: python -m emule_workspace test python --path tests/python/test_amutorrent_browser_smoke.py --quiet passed.
  • 2026-05-13: python -m emule_workspace test live-e2e --config Release --platform x64 --suite amutorrent-browser-smoke --skip-live-seed-refresh passed.