ml-explore / ml-explore/mlx-examples

whisper: numerical parity tests fail with MLX 0.32.0 on Apple Silicon

Open
#1,440 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
9k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

Summary

The Whisper example's numerical-parity tests fail with mlx==0.32.0 on Apple Silicon. The same failures reproduce on a clean checkout of main, so they are independent of PR #1439, where this was discovered.

Environment

  • macOS on Apple Silicon
  • Python 3.14
  • MLX 0.32.0
  • Current main

Reproduction

cd whisper
python -m unittest \
  test.TestWhisper.test_torch_mlx \
  test.TestWhisper.test_decode_lang \
  test.TestWhisper.test_decode_greedy

Observed failures

  • test_torch_mlx: Torch/MLX logits are no longer within the existing 1e-2 tolerance.
    • max absolute difference: ~0.254
    • mean absolute difference: ~0.052
  • test_decode_lang: English probability differs by ~1.1e-4.
  • test_decode_greedy: no-speech probability differs by ~1.7e-4.

The requirements currently allow any mlx>=0.11, so a current installation resolves to MLX 0.32.0.

Expected

Either the Whisper implementation should retain parity with current MLX, or the supported/tested MLX version should be pinned and documented.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in whisper by running the three TestWhisper unittest targets from the reproduction command on Apple Silicon with MLX 0.32.0. Compare the failing Torch/MLX parity and decoding checks with the current requirements constraint, then determine whether the implementation or the supported MLX version needs adjustment. Done means the tests pass within their stated tolerances or the supported version is pinned and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.