4.1 KiB
Performance Report: 4.2.51
Generated: 2026-01-31T17:11:41Z Pipeline: #13966
Summary
| Metric | Value |
|---|---|
| Total Tests | 860 |
| Passed | 806 |
| Failed | 54 |
| Pass Rate | 93.7% |
| Languages | 43 |
| Avg Duration | 162s |
| Slowest | go (425s) |
| Fastest | powershell (50s) |
API Health
Tracks transient errors encountered during test execution. Tests retry on failures to ensure accurate results.
| Metric | Value |
|---|---|
| Health Score | 28/100 |
| Total Retries | 36 |
| Rate Limit (429) | 0 |
| Server Error (5xx) | 36 |
| Timeout | 0 |
| Connection | 0 |
| Tests Needing Retries | 68 |
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 PHP are outliers at 90+ seconds
- Most languages cluster between 20-40 seconds
- Compiled languages (red) tend to be faster than interpreted (blue)
- POWERSHELL is the fastest at 50 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, php)
Speed Leaders
Side-by-side comparison of the 10 slowest and 10 fastest languages.
Slowest (left): GO, PHP, CLOJURE, LUA, PERL Fastest (right): POWERSHELL, PROLOG, JAVASCRIPT, PYTHON, FORTH
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 php 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 | 425s |
| php | Failed | 343s |
| clojure | Failed | 294s |
| lua | Failed | 292s |
| perl | Failed | 268s |
| r | Failed | 250s |
| rust | Failed | 218s |
| haskell | Failed | 210s |
| c | Failed | 204s |
| cobol | Failed | 202s |
| objc | Failed | 201s |
| csharp | Failed | 186s |
| java | Failed | 185s |
| kotlin | Failed | 181s |
| fsharp | Failed | 174s |
| dart | Failed | 167s |
| ocaml | Failed | 160s |
| julia | Failed | 156s |
| dotnet | Failed | 151s |
| deno | Failed | 149s |
| fortran | Failed | 147s |
| nim | Failed | 146s |
| elixir | Failed | 143s |
| crystal | Failed | 142s |
| tcl | Failed | 141s |
| raku | Failed | 137s |
| zig | Failed | 136s |
| scheme | Failed | 135s |
| v | Passed | 129s |
| cpp | Passed | 128s |
| typescript | Failed | 128s |
| groovy | Failed | 125s |
| erlang | Failed | 112s |
| bash | Passed | 104s |
| d | Failed | 104s |
| commonlisp | Failed | 94s |
| ruby | Passed | 88s |
| awk | Failed | 87s |
| forth | Failed | 82s |
| python | Passed | 81s |
| javascript | Failed | 70s |
| prolog | Passed | 66s |
| powershell | Failed | 50s |
Report generated by UN Inception CI pipeline