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 29,303 available1.0%
3 runs needed a re-run2
of 19 workflows2
failed, then passed on re-run123
triggered from forks| Workflow | Runs | Passed | Failed | Re-runs | Recovered | External | Avg runtime (7d) | Flaky rate | |
|---|---|---|---|---|---|---|---|---|---|
| Run Tests (Linux) [on pull request] | 15 | 6 | 9 | 2 | 2 | 10 | 24m 12s | 13.3% | |
| Run Tests (macOS) | 20 | 11 | 9 | 1 | 0 | 9 | 28m 43s | 5.0% | |
| Run Tests (Linux) [on schedule] | 7 | 0 | 7 | 0 | 0 | 0 | 40m 37s | 0.0% | |
| Run Tests (Windows) [on schedule] | 7 | 0 | 7 | 0 | 0 | 0 | 15m 35s | 0.0% | |
| Run Tests (macOS) [on schedule] | 7 | 0 | 7 | 0 | 0 | 0 | 39m 55s | 0.0% | |
| PR Validation | 42 | 13 | 29 | 0 | 0 | 17 | 12s | 0.0% | |
| Build and Test | 21 | 13 | 8 | 0 | 0 | 10 | 20m 52s | 0.0% | |
| Code Coverage [on schedule] | 7 | 5 | 2 | 0 | 0 | 0 | 22m 28s | 0.0% | |
| Check Rebase on Main | 21 | 19 | 2 | 0 | 0 | 10 | 58s | 0.0% | |
| Check Go Generate Has Been Run | 22 | 20 | 2 | 0 | 0 | 10 | 1m 23s | 0.0% | |
| Check for Large Objects | 15 | 14 | 1 | 0 | 0 | 10 | 1m 14s | 0.0% | |
| Web UI E2E Tests | 20 | 19 | 1 | 0 | 0 | 9 | 13m 6s | 0.0% | |
| CodeQL | 23 | 23 | 0 | 0 | 0 | 10 | 2m 57s | 0.0% | |
| Validate Parameters File | 22 | 22 | 0 | 0 | 0 | 10 | 19s | 0.0% | |
| Linter | 21 | 21 | 0 | 0 | 0 | 9 | 3m 2s | 0.0% | |
| Run Tests (Windows) | 20 | 20 | 0 | 0 | 0 | 9 | 9m 57s | 0.0% | |
| Close inactive issues | 6 | 6 | 0 | 0 | 0 | 0 | 20s | 0.0% | |
| Issue Validation | 3 | 3 | 0 | 0 | 0 | 0 | 13s | 0.0% | |
| github_actions in /. - Update #1508686030 | 1 | 1 | 0 | 0 | 0 | 0 | 6m 32s | 0.0% |
