fix(e2e): reach Jellyfin over adb reverse on the API 28 suite
The legacy playback group repeatedly failed to see any Jellyfin server while the container reported healthy, because the API 28 image routes the 10.0.2.2 host alias unreliably. Uses the runner's existing reverse mapping, as the media suite already does on API 35, so the app connects over 127.0.0.1 instead. No assertion is weakened.
This commit is contained in:
@@ -94,6 +94,10 @@ GROUPS: dict[str, tuple[tuple[str, ...], ...]] = {
|
||||
"android-9": (
|
||||
(
|
||||
"basic",
|
||||
# API 28's emulator routing to the 10.0.2.2 host alias is unreliable
|
||||
# on this image, so reach Jellyfin over an adb reverse mapping the
|
||||
# way the media suite already does.
|
||||
"--adb-reverse",
|
||||
"--flow",
|
||||
".maestro/flows/05_playback.yaml",
|
||||
"--jellyfin-log",
|
||||
|
||||
Reference in New Issue
Block a user