Skip to content

ci: Fix TTS smoke test PR comments and simplify validation#504

Merged
Alex-Wengg merged 7 commits intomainfrom
add-rtfx-validation-tts-smoke-tests
Apr 8, 2026
Merged

ci: Fix TTS smoke test PR comments and simplify validation#504
Alex-Wengg merged 7 commits intomainfrom
add-rtfx-validation-tts-smoke-tests

Conversation

@Alex-Wengg
Copy link
Copy Markdown
Member

@Alex-Wengg Alex-Wengg commented Apr 8, 2026

Summary

Updates TTS smoke tests to use always() condition for PR comments, ensuring failure comments are posted even when tests fail.

Changes

Both Kokoro and PocketTTS smoke tests

  • Add always() to PR comment step conditions so they run on failure
  • Move EXECUTION_TIME calculation before any exit points
  • Simplified to only check audio file generation (no RTFx metrics)

Rationale

The original smoke tests had an issue where PR comments would not be posted on failure due to the implicit success() condition in GitHub Actions.

RTFx calculation was removed because:

  • It is a performance metric, not a functional test
  • Smoke tests should verify the pipeline works, not measure performance
  • Simplifies the test and removes ffmpeg dependency

Test Criteria

Smoke tests now pass if:

  1. TTS pipeline completes without crashing
  2. Output WAV file is generated with size greater than 0

Failure scenarios:

  • CLI exits with non-zero code
  • No output file generated
  • Output file size is 0 bytes

Both Kokoro and PocketTTS smoke tests now calculate and validate RTFx metrics:
- Calculate RTFx using ffprobe to get audio duration
- Fail workflow with exit 1 when RTFx is 0
- Display RTFx in PR comment table with status indicator

This ensures TTS smoke tests have the same failure detection as other benchmarks.
devin-ai-integration[bot]

This comment was marked as resolved.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Kokoro TTS Smoke Test ✅

Check Result
Build
Model download
Model load
Synthesis pipeline
Output WAV ✅ (634.8 KB)

Runtime: 0m44s

Note: Kokoro TTS uses CoreML flow matching + Vocos vocoder. CI VM lacks physical ANE — performance may differ from Apple Silicon.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Parakeet EOU Benchmark Results ✅

Status: Benchmark passed
Chunk Size: 320ms
Files Tested: 100/100

Performance Metrics

Metric Value Description
WER (Avg) 7.03% Average Word Error Rate
WER (Med) 4.17% Median Word Error Rate
RTFx 8.40x Real-time factor (higher = faster)
Total Audio 470.6s Total audio duration processed
Total Time 57.1s Total processing time

Streaming Metrics

Metric Value Description
Avg Chunk Time 0.057s Average chunk processing time
Max Chunk Time 0.114s Maximum chunk processing time
EOU Detections 0 Total End-of-Utterance detections

Test runtime: 1m5s • 04/08/2026, 12:57 AM EST

RTFx = Real-Time Factor (higher is better) • Processing includes: Model inference, audio preprocessing, state management, and file I/O

… PR comments

- Move EXECUTION_TIME calculation before RTFx validation to ensure it's set even on failure
- Add always() condition to Comment PR steps so they run even when RTFx validation fails
- Ensures PR comments are posted with failure details instead of silently skipping
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Speaker Diarization Benchmark Results

Speaker Diarization Performance

Evaluating "who spoke when" detection accuracy

Metric Value Target Status Description
DER 15.1% <30% Diarization Error Rate (lower is better)
JER 24.9% <25% Jaccard Error Rate
RTFx 24.71x >1.0x Real-Time Factor (higher is faster)

Diarization Pipeline Timing Breakdown

Time spent in each stage of speaker diarization

Stage Time (s) % Description
Model Download 9.896 23.3 Fetching diarization models
Model Compile 4.241 10.0 CoreML compilation
Audio Load 0.072 0.2 Loading audio file
Segmentation 12.731 30.0 Detecting speech regions
Embedding 21.218 50.0 Extracting speaker voices
Clustering 8.487 20.0 Grouping same speakers
Total 42.464 100 Full pipeline

Speaker Diarization Research Comparison

Research baselines typically achieve 18-30% DER on standard datasets

Method DER Notes
FluidAudio 15.1% On-device CoreML
Research baseline 18-30% Standard dataset performance

Note: RTFx shown above is from GitHub Actions runner. On Apple Silicon with ANE:

  • M2 MacBook Air (2022): Runs at 150 RTFx real-time
  • Performance scales with Apple Neural Engine capabilities

🎯 Speaker Diarization Test • AMI Corpus ES2004a • 1049.0s meeting audio • 42.4s diarization time • Test runtime: 2m 18s • 04/08/2026, 12:54 AM EST

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

ASR Benchmark Results ✅

Status: All benchmarks passed

Parakeet v3 (multilingual)

Dataset WER Avg WER Med RTFx Status
test-clean 0.57% 0.00% 4.90x
test-other 1.35% 0.00% 3.23x

Parakeet v2 (English-optimized)

Dataset WER Avg WER Med RTFx Status
test-clean 0.80% 0.00% 4.79x
test-other 1.40% 0.00% 2.88x

Streaming (v3)

Metric Value Description
WER 0.00% Word Error Rate in streaming mode
RTFx 0.54x Streaming real-time factor
Avg Chunk Time 1.688s Average time to process each chunk
Max Chunk Time 2.293s Maximum chunk processing time
First Token 2.006s Latency to first transcription token
Total Chunks 31 Number of chunks processed

Streaming (v2)

Metric Value Description
WER 0.00% Word Error Rate in streaming mode
RTFx 0.50x Streaming real-time factor
Avg Chunk Time 1.772s Average time to process each chunk
Max Chunk Time 2.164s Maximum chunk processing time
First Token 1.793s Latency to first transcription token
Total Chunks 31 Number of chunks processed

Streaming tests use 5 files with 0.5s chunks to simulate real-time audio streaming

25 files per dataset • Test runtime: 6m33s • 04/08/2026, 01:00 AM EST

RTFx = Real-Time Factor (higher is better) • Calculated as: Total audio duration ÷ Total processing time
Processing time includes: Model inference on Apple Neural Engine, audio preprocessing, state resets between files, token-to-text conversion, and file I/O
Example: RTFx of 2.0x means 10 seconds of audio processed in 5 seconds (2x faster than real-time)

Expected RTFx Performance on Physical M1 Hardware:

• M1 Mac: ~28x (clean), ~25x (other)
• CI shows ~0.5-3x due to virtualization limitations

Testing methodology follows HuggingFace Open ASR Leaderboard

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Qwen3-ASR int8 Smoke Test ✅

Check Result
Build
Model download
Model load
Transcription pipeline
Decoder size 571 MB (vs 1.1 GB f32)

Performance Metrics

Metric CI Value Expected on Apple Silicon
Median RTFx 0.04x ~2.5x
Overall RTFx 0.04x ~2.5x

Runtime: 5m17s

Note: CI VM lacks physical GPU — CoreML MLState (macOS 15) KV cache produces degraded results on virtualized runners. On Apple Silicon: ~1.3% WER / 2.5x RTFx.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Sortformer High-Latency Benchmark Results

ES2004a Performance (30.4s latency config)

Metric Value Target Status
DER 33.4% <35%
Miss Rate 24.4% - -
False Alarm 0.2% - -
Speaker Error 8.8% - -
RTFx 7.6x >1.0x
Speakers 4/4 - -

Sortformer High-Latency • ES2004a • Runtime: 3m 19s • 2026-04-08T04:55:40.053Z

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

PocketTTS Smoke Test ✅

Check Result
Build
Model download
Model load
Synthesis pipeline
Output WAV ✅ (172.5 KB)

Runtime: 0m31s

Note: PocketTTS uses CoreML MLState (macOS 15) KV cache + Mimi streaming state. CI VM lacks physical GPU — audio quality and performance may differ from Apple Silicon.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

VAD Benchmark Results

Performance Comparison

Dataset Accuracy Precision Recall F1-Score RTFx Files
MUSAN 92.0% 86.2% 100.0% 92.6% 757.1x faster 50
VOiCES 92.0% 86.2% 100.0% 92.6% 780.5x faster 50

Dataset Details

  • MUSAN: Music, Speech, and Noise dataset - standard VAD evaluation
  • VOiCES: Voices Obscured in Complex Environmental Settings - tests robustness in real-world conditions

✅: Average F1-Score above 70%

- Run 'brew link ffmpeg' to ensure ffprobe is in PATH
- Add debugging to show ffprobe availability and output
- Change 2>/dev/null to 2>&1 to capture ffprobe errors
- Add detailed logging when RTFx calculation fails

This fixes the issue where ffmpeg was installed but not linked,
causing ffprobe to be unavailable and RTFx calculation to fail.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Offline VBx Pipeline Results

Speaker Diarization Performance (VBx Batch Mode)

Optimal clustering with Hungarian algorithm for maximum accuracy

Metric Value Target Status Description
DER 14.5% <20% Diarization Error Rate (lower is better)
RTFx 4.05x >1.0x Real-Time Factor (higher is faster)

Offline VBx Pipeline Timing Breakdown

Time spent in each stage of batch diarization

Stage Time (s) % Description
Model Download 15.378 5.9 Fetching diarization models
Model Compile 6.590 2.5 CoreML compilation
Audio Load 0.115 0.0 Loading audio file
Segmentation 31.419 12.1 VAD + speech detection
Embedding 258.215 99.6 Speaker embedding extraction
Clustering (VBx) 0.948 0.4 Hungarian algorithm + VBx clustering
Total 259.368 100 Full VBx pipeline

Speaker Diarization Research Comparison

Offline VBx achieves competitive accuracy with batch processing

Method DER Mode Description
FluidAudio (Offline) 14.5% VBx Batch On-device CoreML with optimal clustering
FluidAudio (Streaming) 17.7% Chunk-based First-occurrence speaker mapping
Research baseline 18-30% Various Standard dataset performance

Pipeline Details:

  • Mode: Offline VBx with Hungarian algorithm for optimal speaker-to-cluster assignment
  • Segmentation: VAD-based voice activity detection
  • Embeddings: WeSpeaker-compatible speaker embeddings
  • Clustering: PowerSet with VBx refinement
  • Accuracy: Higher than streaming due to optimal post-hoc mapping

🎯 Offline VBx Test • AMI Corpus ES2004a • 1049.0s meeting audio • 290.6s processing • Test runtime: 4m 52s • 04/08/2026, 01:10 AM EST

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 new potential issues.

View 7 additional findings in Devin Review.

Open in Devin Review

- Force-link ffmpeg with --force flag to ensure it's linked
- Set explicit PATH environment variable in smoke test steps
- Validate ffprobe output is numeric before passing to awk
- Prevents awk syntax errors when ffprobe returns error messages

This fixes the issue where ffprobe wasn't available in PATH even
after installation, causing RTFx calculation to fail.
- Remove exit 1 when RTFx is 0
- Change RTFx status from ❌ to ⚠️ when unavailable
- RTFx is a performance metric, not a pass/fail criterion
- Smoke tests pass as long as audio is generated (file size > 0)

This aligns with the purpose of smoke tests: verify the pipeline
works, not measure performance.
- Remove all RTFx calculation logic
- Remove ffmpeg/ffprobe installation steps
- Remove RTFx from PR comment tables
- Simplify smoke tests to only verify audio file generation

Smoke tests now pass if:
1. TTS pipeline completes without crashing
2. Output WAV file is generated with size > 0

RTFx is a performance metric better suited for benchmark workflows,
not smoke tests.
@Alex-Wengg Alex-Wengg changed the title ci: Add RTFx validation to TTS smoke tests ci: Fix TTS smoke test PR comments and simplify validation Apr 8, 2026
- Add validation that exits with code 1 when output file doesn't exist
- Add validation that exits with code 1 when output file is 0 bytes
- Ensures smoke tests fail on audio generation failures

This catches cases where the pipeline runs but produces no/empty output.
@Alex-Wengg Alex-Wengg merged commit 2c686cd into main Apr 8, 2026
12 checks passed
@Alex-Wengg Alex-Wengg deleted the add-rtfx-validation-tts-smoke-tests branch April 8, 2026 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant