llm/skills: add skill for debugging buildkite/ci failures#35248
Merged
aljoscha merged 1 commit intoMaterializeInc:mainfrom Mar 2, 2026
Merged
llm/skills: add skill for debugging buildkite/ci failures#35248aljoscha merged 1 commit intoMaterializeInc:mainfrom
aljoscha merged 1 commit intoMaterializeInc:mainfrom
Conversation
|
Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone. PR title guidelines
Pre-merge checklist
|
antiguru
reviewed
Feb 27, 2026
Member
antiguru
left a comment
antiguru
left a comment
There was a problem hiding this comment.
Dis you figure out a way for the cli to fetch artifacts? I failed because it'd need graphql permissions.
Contributor
Author
I fixed this by giving the token graphql access. It doesn't allow limiting by scopes, but ... 🤷♂️ |
antiguru
approved these changes
Feb 27, 2026
def-
reviewed
Feb 27, 2026
Comment on lines
11
to
31
| ## Step 1: Extract PR number | ||
|
|
||
| Parse `$ARGUMENTS` to get the PR number. Handle both formats: | ||
| - Plain number: `35192` | ||
| - Full URL: `https://github.com/MaterializeInc/materialize/pull/35192` | ||
|
|
||
| ## Step 2: List failing checks | ||
|
|
||
| ```bash | ||
| gh pr checks <PR_NUMBER> 2>&1 | ||
| ``` | ||
|
|
||
| Filter the output to lines containing `fail`. Each line has tab-separated fields: | ||
| ``` | ||
| name fail 0 https://buildkite.com/materialize/<PIPELINE>/builds/<BUILD>#<JOB_ID> description | ||
| ``` | ||
|
|
||
| Extract from the URL: | ||
| - **Pipeline**: path segment after `materialize/` (usually `test`) | ||
| - **Build number**: the number after `builds/` | ||
| - **Job ID**: the UUID after `#` |
Contributor
There was a problem hiding this comment.
It might be easier to just do
bk build list --branch=def-:pr-fix-secret-cli
where def- is the username of my fork and pr-fix-secret-cli the branch name, instead of these github api roundtrips.
Contributor
Author
There was a problem hiding this comment.
Claude said it wouldn't want to add this, because it's to complicated to know the username of the fork, but we did incorporate the other suggestions. 🙇♂️
def-
reviewed
Feb 27, 2026
.claude/skills/debug-ci/SKILL.md
Outdated
| - **Build number**: the number after `builds/` | ||
| - **Job ID**: the UUID after `#` | ||
|
|
||
| ## Step 3: Fetch logs in triage order |
Contributor
There was a problem hiding this comment.
I would look at the annotation for test failures first, before looking into logs. Can save you a bunch of tokens or grepping around.
def-
reviewed
Feb 27, 2026
.claude/skills/debug-ci/SKILL.md
Outdated
| ### Testdrive cascades | ||
| After one test crashes environmentd, all subsequent tests in that shard fail with `Name or service not known` or `connection closed`. **Only the first failure in a shard matters** — everything after it is a cascade. Look for the first `error:` or `FAIL` in the log. | ||
|
|
||
| Testdrive shards with the same number (e.g., `testdrive-10` and `testdrive-with-alloydb-10`) run the same tests — if both fail, it's the same root cause. |
Contributor
There was a problem hiding this comment.
Suggested change
| Testdrive shards with the same number (e.g., `testdrive-10` and `testdrive-with-alloydb-10`) run the same tests — if both fail, it's the same root cause. | |
| Testdrive shards with the same number (e.g., `testdrive-10` and `testdrive-with-alloydb-10`) run the same tests — if both fail, it's likely to be the same root cause. |
def-
reviewed
Feb 27, 2026
.claude/skills/debug-ci/SKILL.md
Outdated
| 1. **Root cause A** — description, which jobs it affects, what to fix | ||
| 2. **Root cause B** — description, which jobs it affects, what to fix | ||
|
|
||
| Distinguish between issues that are clearly caused by the PR's changes vs. pre-existing flaky tests. |
Contributor
There was a problem hiding this comment.
Pre-existing flaky tests can often be discovered through the annotations, which will link to the issue that is causing it.
aljoscha
force-pushed
the
push-srwssurrzvmx
branch
from
5f48e2d to
320c6dd
Compare
aljoscha
force-pushed
the
push-srwssurrzvmx
branch
from
320c6dd to
b6d0a08
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.