Case

sendspin-server-cpp -> sendspin-js

Start the server first, then the client. The client connects, advertises two PCM formats (24-bit then 16-bit), and the server starts streaming the higher-priority 24-bit format. The client then sends a client/state whose player format prefers the 16-bit entry. The matrix verifies the server received that preference in client/state and the client observed a new stream/start in the 16-bit format.

Server

sendspin-server-cpp

Client

sendspin-js

Status

Failed

Server adapter reported: no client completed the handshake with a client/hello; Client adapter reported: sendspin-js adapter does not support scenario client-initiated-state-format-pcm through the public SDK.

Inspection

Summaries, logs, and builds

Matrix result

RAW
{
  "case_dir": "artifacts/results/data/macos__client-initiated-state-format-pcm__sendspin-server-cpp__to__sendspin-js",
  "client_exit_code": 1,
  "client_impl": "sendspin-js",
  "reason": "Server adapter reported: no client completed the handshake with a client/hello; Client adapter reported: sendspin-js adapter does not support scenario client-initiated-state-format-pcm through the public SDK.",
  "scenario_id": "client-initiated-state-format-pcm",
  "scenario_revision": 5,
  "server_exit_code": 1,
  "server_impl": "sendspin-server-cpp",
  "status": "failed",
  "unsupported": false
}