issue_id stringlengths 6 6 | title stringlengths 14 33 | status stringclasses 3
values | failure_category stringclasses 9
values | created_date stringdate 2025-03-03 00:00:00 2025-04-01 00:00:00 | resolved_date stringclasses 5
values | priority stringclasses 3
values |
|---|---|---|---|---|---|---|
WF-001 | Test timeout in suite A | open | test_timeout | 2025-03-03 | null | high |
WF-002 | Deploy failed due to config | open | deployment error | 2025-03-04 | null | medium |
WF-003 | Configuration error in YAML | open | build-failure | 2025-03-05 | null | high |
WF-004 | Random pipeline crash | open | null | 2025-03-06 | null | low |
WF-005 | Build failure on main | duplicate | build_failure | 2025-03-07 | 2025-03-08 | low |
WF-006 | Test timeout in suite A | open | test_timeout | 2025-03-08 | null | low |
WF-007 | deployment_failure staging | open | test-timeout | 2025-03-09 | null | high |
WF-008 | Configuration error in YAML | open | configuration_error | 2025-03-10 | null | high |
WF-009 | Random pipeline crash | open | null | 2025-03-11 | null | high |
WF-010 | Build failure on main | open | build_failure | 2025-03-12 | null | low |
WF-011 | Test-timeout during integration | open | test_timeout | 2025-03-13 | null | low |
WF-012 | Deploy failed due to config | closed | deployment error | 2025-03-14 | 2025-03-15 | low |
WF-013 | Wrong config for DB | open | configuration_error | 2025-03-15 | null | medium |
WF-014 | Random pipeline crash | open | deploy_error | 2025-03-16 | null | medium |
WF-015 | CI build error | open | build_failure | 2025-03-17 | null | high |
WF-016 | Test-timeout during integration | open | test_timeout | 2025-03-18 | null | low |
WF-017 | deployment_failure staging | open | deployment error | 2025-03-19 | null | medium |
WF-018 | config_error: missing env | closed | configuration_error | 2025-03-20 | 2025-03-21 | high |
WF-019 | Random pipeline crash | open | null | 2025-03-21 | null | medium |
WF-020 | Build failure on main | open | build_failure | 2025-03-22 | null | high |
WF-021 | test timeout: database connection | open | config error | 2025-03-23 | null | high |
WF-022 | deployment_failure staging | open | deployment error | 2025-03-24 | null | medium |
WF-023 | Wrong config for DB | open | configuration_error | 2025-03-25 | null | medium |
WF-024 | Random pipeline crash | open | null | 2025-03-26 | null | low |
WF-025 | build-failure on staging | duplicate | build_failure | 2025-03-27 | 2025-03-28 | low |
WF-026 | Test timeout in suite A | open | test_timeout | 2025-03-28 | null | medium |
WF-027 | Deployment error on dev | open | deployment error | 2025-03-29 | null | low |
WF-028 | config_error: missing env | open | build failure | 2025-03-30 | null | low |
WF-029 | Unexpected error | open | null | 2025-03-31 | null | low |
WF-030 | Build failed for feature X | closed | build_failure | 2025-04-01 | 2025-04-02 | low |
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
Workflow Failure Issue Triage
This dataset contains CI/CD workflow failure issues for the past month. This README serves as the auto-generated summary report.
Executive Summary
- Reporting period: Mar 03, 2025 – Apr 01, 2025 — 30 issues logged; 25 valid issues analyzed (Mar 03, 2025 – Mar 31, 2025).
- Excluded: 5 issues (3 closed, 2 duplicates) removed from analysis.
- Top root cause: Test Timeout (6 issues, 24% of valid), followed by Build Failure and Deployment Error (5 each).
- Volume: failure flow was steady at ~6 issues/week across the four full weeks, then dropped to 1 in the final partial week.
- Attention: 5 issues (20%) could not be classified (e.g. "Random pipeline crash", "Unexpected error") — consider extending the triage rules to capture these.
Classification Counts (25 valid issues)
| Root Cause | Count | Share of Valid |
|---|---|---|
| Build Failure | 5 | 20% |
| Test Timeout | 6 | 24% |
| Deployment Error | 5 | 20% |
| Configuration Error | 4 | 16% |
| Unknown | 5 | 20% |
| Total | 25 | 100% |
Weekly Breakdown
| Week (Mon–Sun) | Build Failure | Test Timeout | Deployment Error | Configuration Error | Unknown | Total |
|---|---|---|---|---|---|---|
| Mar 03 – Mar 09 | 1 | 3 | 1 | 0 | 1 | 6 |
| Mar 10 – Mar 16 | 1 | 1 | 1 | 2 | 1 | 6 |
| Mar 17 – Mar 23 | 2 | 1 | 1 | 1 | 1 | 6 |
| Mar 24 – Mar 30 | 1 | 1 | 2 | 1 | 1 | 6 |
| Mar 31 – Apr 06 (partial) | 0 | 0 | 0 | 0 | 1 | 1 |
| Total | 5 | 6 | 5 | 4 | 5 | 25 |
Week-over-Week Observations
- Test Timeout spiked in the week of Mar 3 (3 issues), then settled to a steady 1/week — the most recurring failure category.
- Build Failure peaked in the week of Mar 17 (2 issues); otherwise 1/week.
- Deployment Error peaked in the week of Mar 24 (2 issues); otherwise 1/week.
- Configuration Error peaked in the week of Mar 10 (2 issues), then held at 1/week.
- Unclassified issues remained a constant ~1/week throughout — a persistent triage gap worth addressing.
Excluded from Analysis
| Issue | Title | Created | Status | Reason |
|---|---|---|---|---|
| WF-005 | Build failure on main | 2025-03-07 | duplicate | Duplicate of another issue |
| WF-012 | Deploy failed due to config | 2025-03-14 | closed | Already closed / resolved |
| WF-018 | config_error: missing env | 2025-03-20 | closed | Already closed / resolved |
| WF-025 | build-failure on staging | 2025-03-27 | duplicate | Duplicate of another issue |
| WF-030 | Build failed for feature X | 2025-04-01 | closed | Already closed / resolved |
Excluded total: 5 issues — 3 closed, 2 duplicates. Exclusions are applied to all counts above.
Methodology
- Failure categories were normalized with fuzzy matching per
rules.txt(e.g.build_failure,build-failure,build failure→ Build Failure). - When a category was missing, the title was classified by keywords (
build,timeout,deploy,config); otherwise the issue was marked Unknown. - Issues with status
closedorduplicatewere excluded from all counts.
- Downloads last month
- 47