Voice 13: interop tests have not been run against livekit-server (agent may not download and run it) #120

Closed
opened 2026-11-11 20:17:23 +00:00 by charles · 1 comment
Owner

Voice 13 (#74) asks for the LiveKit interop tests to pass locally against livekit-server v1.12.0 before the PR goes up. The implementing agent could not do that step: downloading and running the livekit-server release binary was refused by the agent's permission system (running code downloaded from outside), and it did not look for a way around that.

State of the branch voice-13-voice-livekit-interop

  • LiveKitRoom, VoiceSession::livekit, fluxer_voice::apm, tools/livekit-test-server.sh, the xtask step and the CI changes are written; FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci is green locally, including 13 unit tests of the room that need no server.
  • The five interop tests in crates/fluxer-voice/tests/livekit_interop.rs compile and are clippy-clean but have never been run against a server. Neither has tools/livekit-test-server.sh (only bash -n), nor the new Linux CI steps (clang 21 from apt.llvm.org, libglib2.0-dev, the server download).

What is needed from Charles — one of:

  1. Run them once by hand in the worktree and report what fails:
    tools/livekit-test-server.sh &
    FLUXER_LIVEKIT_TESTS=1 cargo test -p fluxer-voice --test livekit_interop -- --ignored --test-threads=1
    
    (or FLUXER_LIVEKIT_TESTS=1 cargo xtask ci, which starts and stops the server itself);
  2. allow agents to download and run that binary (a permission rule for tools/livekit-test-server.sh), so the implementer or reviewer can run them; or
  3. accept the Linux runner as the first real run of these tests and fix forward from its log.

Things most likely to need adjusting on a first run: the server flags in the script (--dev --bind 127.0.0.1 --node-ip 127.0.0.1), the timing margins in the tests, and whether a data packet sent right after Connected reaches the other participant within 3 s.

Voice 13 (#74) asks for the LiveKit interop tests to pass locally against `livekit-server` v1.12.0 before the PR goes up. The implementing agent could not do that step: downloading and running the `livekit-server` release binary was refused by the agent's permission system (running code downloaded from outside), and it did not look for a way around that. **State of the branch `voice-13-voice-livekit-interop`** - `LiveKitRoom`, `VoiceSession::livekit`, `fluxer_voice::apm`, `tools/livekit-test-server.sh`, the xtask step and the CI changes are written; `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` is green locally, including 13 unit tests of the room that need no server. - The five interop tests in `crates/fluxer-voice/tests/livekit_interop.rs` compile and are clippy-clean but **have never been run against a server**. Neither has `tools/livekit-test-server.sh` (only `bash -n`), nor the new Linux CI steps (clang 21 from apt.llvm.org, `libglib2.0-dev`, the server download). **What is needed from Charles — one of:** 1. Run them once by hand in the worktree and report what fails: ``` tools/livekit-test-server.sh & FLUXER_LIVEKIT_TESTS=1 cargo test -p fluxer-voice --test livekit_interop -- --ignored --test-threads=1 ``` (or `FLUXER_LIVEKIT_TESTS=1 cargo xtask ci`, which starts and stops the server itself); 2. allow agents to download and run that binary (a permission rule for `tools/livekit-test-server.sh`), so the implementer or reviewer can run them; or 3. accept the Linux runner as the first real run of these tests and fix forward from its log. Things most likely to need adjusting on a first run: the server flags in the script (`--dev --bind 127.0.0.1 --node-ip 127.0.0.1`), the timing margins in the tests, and whether a data packet sent right after `Connected` reaches the other participant within 3 s.
Author
Owner

Done on textchat (c24495a): ci.yaml:49-52: FLUXER_LIVEKIT_TESTS=1, cargo xtask ci starts livekit-server v1.12.0. The interop results quoted in #125 and #223 also came from these runs

Closed during the 2026-11-14 issue triage.

🤖 Generated with Claude Code

Done on `textchat` (c24495a): `ci.yaml:49-52`: `FLUXER_LIVEKIT_TESTS=1`, `cargo xtask ci` starts livekit-server v1.12.0. The interop results quoted in #125 and #223 also came from these runs Closed during the 2026-11-14 issue triage. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#120
No description provided.