4.1 KiB
Performance Report: 4.3.3
Generated: 2026-02-08T19:28:06Z Pipeline: #15719
Summary
| Metric | Value |
|---|---|
| Total Tests | 848 |
| Passed | 806 |
| Failed | 42 |
| Pass Rate | 95.0% |
| Languages | 43 |
| Avg Duration | 175s |
| Slowest | go (447s) |
| Fastest | v (65s) |
API Health
Tracks transient errors encountered during test execution. Tests retry on failures to ensure accurate results.
| Metric | Value |
|---|---|
| Health Score | 0/100 |
| Total Retries | 330 |
| Rate Limit (429) | 320 |
| Server Error (5xx) | 0 |
| Timeout | 10 |
| Connection | 0 |
| Tests Needing Retries | 116 |
Interpretation:
- Score 95-100: API is healthy, minimal transient errors
- Score 80-94: Some API instability, but tests recovered via retry
- Score < 80: Significant API issues affecting test reliability
Test Duration by Language
The primary performance metric - how long each language takes to run its full test suite (15 tests per language).
Key observations:
- GO and CRYSTAL are outliers at 90+ seconds
- Most languages cluster between 20-40 seconds
- Compiled languages (red) tend to be faster than interpreted (blue)
- V is the fastest at 65 seconds
Compiled vs Interpreted
Comparing performance between compiled languages (C, Go, Rust, etc.) and interpreted languages (Python, Ruby, JavaScript, etc.).
Findings:
- 20 compiled languages vs 22 interpreted
- Compiled languages have lower median execution time
- Interpreted languages show more variance (wider spread)
- The white diamond marks the mean for each category
Duration Distribution
Histogram showing how test durations are distributed across all 43 languages.
Distribution analysis:
- Most languages complete in 20-35 seconds (the peak)
- Mean (green dashed) and median (blue dotted) are close together
- Long tail on the right from slow outliers (go, crystal)
Speed Leaders
Side-by-side comparison of the 10 slowest and 10 fastest languages.
Slowest (left): GO, CRYSTAL, RAKU, TYPESCRIPT, KOTLIN Fastest (right): V, R, DART, PERL, RUST
Queue vs Execution Time
Scatter plot showing the relationship between CI queue wait time and actual test execution time.
Notes:
- Queue time is how long the job waited for a runner
- Most jobs had similar queue times (clustered vertically)
- Outliers labeled - go and crystal took longest to execute regardless of queue time
Dashboard
Summary dashboard combining key metrics and visualizations.
Raw Data
Per-Language Performance
| Language | Status | Duration |
|---|---|---|
| go | Failed | 447s |
| crystal | Failed | 347s |
| raku | Failed | 306s |
| typescript | Failed | 296s |
| kotlin | Failed | 283s |
| clojure | Failed | 273s |
| groovy | Failed | 268s |
| commonlisp | Failed | 238s |
| erlang | Failed | 237s |
| java | Passed | 217s |
| cobol | Failed | 208s |
| javascript | Failed | 202s |
| lua | Failed | 198s |
| deno | Failed | 198s |
| scheme | Failed | 196s |
| tcl | Failed | 186s |
| fortran | Failed | 186s |
| prolog | Passed | 185s |
| ocaml | Failed | 174s |
| cpp | Passed | 165s |
| forth | Failed | 160s |
| bash | Passed | 159s |
| python | Passed | 158s |
| julia | Failed | 152s |
| ruby | Passed | 149s |
| fsharp | Failed | 146s |
| php | Passed | 140s |
| csharp | Failed | 136s |
| dotnet | Failed | 130s |
| d | Failed | 130s |
| awk | Failed | 119s |
| elixir | Failed | 117s |
| objc | Failed | 114s |
| zig | Failed | 112s |
| haskell | Failed | 110s |
| powershell | Failed | 103s |
| c | Passed | 100s |
| nim | Failed | 91s |
| rust | Failed | 87s |
| perl | Passed | 86s |
| dart | Failed | 85s |
| r | Passed | 81s |
| v | Passed | 65s |
Report generated by UN Inception CI pipeline