Skip to content

fix(typo): corrects readme#1

Merged
JAORMX merged 1 commit into
mainfrom
readme-typo
Mar 22, 2025
Merged

fix(typo): corrects readme#1
JAORMX merged 1 commit into
mainfrom
readme-typo

Conversation

@ChrisJBurns
Copy link
Copy Markdown
Collaborator

  • my first commit, wohoo

- my first commit, wohoo

Signed-off-by: ChrisJBurns <29541485+ChrisJBurns@users.noreply.github.com>
@ChrisJBurns ChrisJBurns changed the title chore(typo) corrects readme fix(typo): corrects readme Mar 22, 2025
@kofort9
Copy link
Copy Markdown
Contributor

kofort9 commented Oct 18, 2025

Update: Bug Fix Separated

I've created a separate PR for the nil pointer dereference fix: #2252

This PR (#1) will remain as a draft until the bug fix is merged and available in a release. Once that's done, we can:

  1. Update this PR to use the new release
  2. Test the Actions migration properly
  3. Remove the legacy Docker code after validation

This separation makes it easier to review and merge the critical bug fix independently.

@jerm-dro jerm-dro mentioned this pull request Mar 17, 2026
2 tasks
jerm-dro added a commit that referenced this pull request Apr 10, 2026
Adds a /deflake skill that analyzes GitHub Actions failures on main to
discover, rank, and plan fixes for flaky tests. The skill includes a
Python collection script that deterministically fetches failed run logs
in parallel, extracts test names from Ginkgo and gotestfmt output, and
aggregates failures into a ranked report.

Used this skill to identify and fix the #1 flake (workload lifecycle
E2E test, 12/147 runs) in #4745.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jerm-dro added a commit that referenced this pull request Apr 10, 2026
* Add deflake skill for finding and fixing flaky tests

Adds a /deflake skill that analyzes GitHub Actions failures on main to
discover, rank, and plan fixes for flaky tests. The skill includes a
Python collection script that deterministically fetches failed run logs
in parallel, extracts test names from Ginkgo and gotestfmt output, and
aggregates failures into a ranked report.

Used this skill to identify and fix the #1 flake (workload lifecycle
E2E test, 12/147 runs) in #4745.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Address review feedback on collect-flakes script

- Extract per-test log context (50 lines before the failure marker)
  before classifying failure mode, so tests in the same run get
  accurate individual mode labels instead of all inheriting the
  first match from the full run log
- Add try/except around future.result() so one failed run doesn't
  crash the script and lose all collected data
- Fix misleading comment about MAX_PAGES covering 300 Main build
  runs — the API returns all workflows' runs, not just Main build

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Fix per-test failure mode extraction in collect-flakes

The previous attempt to extract per-test failure context used a 50-line
window before the [FAIL] summary line, but Ginkgo's [FAILED] reason
line (e.g., "Timed out after 120s") can appear thousands of lines
earlier. Also needed ANSI stripping when searching for [FAILED] markers.

Now searches backwards from the [FAIL] summary to find all [FAILED]
lines in the failure block, uses the earliest one (which has the
actual failure reason), and extracts context spanning all of them.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants