The GitHub Actions workflows in PelicanPlatform/pelican — how often their runs pass, how long they take, and how reliable they are. Workflows are ranked by flaky rate: a run that fails and then passes on retry, without any code change, is the clearest sign of an unreliable test or pipeline.
300
of 31,023 available0.7%
2 runs needed a re-run2
of 19 workflows2
failed, then passed on re-run194
triggered from forks| Workflow | Runs | Passed | Failed | Re-runs | Recovered | External | Avg runtime (7d) | Flaky rate | |
|---|---|---|---|---|---|---|---|---|---|
| Run Tests (Linux) [on pull request] | 15 | 9 | 5 | 1 | 1 | 15 | 20m 34s | 6.7% | |
| Linter | 25 | 20 | 4 | 1 | 1 | 16 | 2m 58s | 4.0% | |
| Run Tests (Linux) [on schedule] | 5 | 0 | 5 | 0 | 0 | 0 | 41m 19s | 0.0% | |
| Run Tests (Windows) [on schedule] | 5 | 0 | 5 | 0 | 0 | 0 | 16m 48s | 0.0% | |
| Run Tests (macOS) [on schedule] | 5 | 0 | 5 | 0 | 0 | 0 | 47m 14s | 0.0% | |
| PR Validation | 22 | 9 | 12 | 0 | 0 | 22 | 22s | 0.0% | |
| Run Tests (macOS) | 26 | 17 | 8 | 0 | 0 | 17 | 26m 59s | 0.0% | |
| Build and Test | 24 | 18 | 5 | 0 | 0 | 16 | 25m 8s | 0.0% | |
| Check Rebase on Main | 14 | 11 | 2 | 0 | 0 | 10 | 10s | 0.0% | |
| CodeQL | 21 | 18 | 2 | 0 | 0 | 11 | 2m 28s | 0.0% | |
| Check Go Generate Has Been Run | 27 | 24 | 2 | 0 | 0 | 18 | 1m 56s | 0.0% | |
| Run Tests (Windows) | 26 | 24 | 1 | 0 | 0 | 17 | 9m 47s | 0.0% | |
| Web UI E2E Tests | 27 | 25 | 1 | 0 | 0 | 19 | 11m 20s | 0.0% | |
| Validate Parameters File | 26 | 25 | 0 | 0 | 0 | 17 | 16s | 0.0% | |
| Check for Large Objects | 16 | 15 | 0 | 0 | 0 | 16 | 12s | 0.0% | |
| Issue Validation | 5 | 5 | 0 | 0 | 0 | 0 | 10s | 0.0% | |
| Code Coverage [on schedule] | 5 | 5 | 0 | 0 | 0 | 0 | 22m 19s | 0.0% | |
| Close inactive issues | 5 | 5 | 0 | 0 | 0 | 0 | 17s | 0.0% | |
| Generate Release Artifacts | 1 | 1 | 0 | 0 | 0 | 0 | 13m 24s | 0.0% |
