You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[shared-ci] mutation failing across hivecommons/hive #17463
Summary: An optional quality check that runs on every proposed change keeps getting stopped part-way because it hits its 20-minute time limit. Changes that do not touch the code it tests are hit too. It shows up as red even though it never judged the change, which sends contributors looking for problems that aren't there.
What I need from you: Raise the time limit, or limit the check to the files a change actually touches.
Recent mutation-advisory.yml runs on pull_request ended cancelled on branches scanner/fix-17426, fix/17450-stage-workflow-pat-prs, fix/merge-train-defer-duplicate-holds-17439 (×2), scanner/fix-17433, fix/needs-human-real-stage and fix/merge-train-duplicate-per-base. Some of these may be cancel-in-progress after a newer push; the 🐛 fix(automerge): hold same-issue PRs only at the merge gate and keep the pick #17444 run is a timeout.
Likely cause: the job mutates the whole changed package (here src/pkg/github/automerge, a large package), so it can't finish in 20 minutes.
Summary: A second open change hit the same time limit on the same optional check, which confirms this is a repository-wide problem rather than one change's fault.
#17454, job 129476754049: started 22:14:15Z, cancelled at the 20-minute limit at 22:34:27Z while mutating advisory.go, which #17454 does not change.
Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label triage/accepted (configured in issue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.
A third timeout, on #17479 (run 42724392644, job 129526278555). It hit the 20-minute limit while still on advisory.go, a file #17479 does not touch.
#17479 changes src/pkg/github/pr_decision_operator.go. Because mutation-report.sh keeps only the top-most package directory and gremlins walks every file under it, the job ran gremlins unleash ./pkg/github. That covers all of pkg/github plus pkg/github/automerge and its other subpackages. Collecting coverage alone took 1m29s, and it got through only part of advisory.go in the time left.
A note for whoever limits the check to changed lines: gremlins v0.6.0 has --diff <ref>, but plain --diff origin/$BASE_REF will skip every mutant here. The diff is read from git diff --merge-base <ref>, which gives paths from the repo root (src/pkg/github/x.go). gremlins compares those against paths relative to the directory it was run on (x.go), per internal/diff/parse.go and internal/engine/engine.go (os.DirFS(Root/CallingDir)). Two ways around it: run gremlins from inside the package directory with GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=diff.relative GIT_CONFIG_VALUE_0=true set, so git diff prints paths relative to that directory, or pass --exclude-files for every unchanged file.
@Karibhou this issue was closed by @kubestellar-prow[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
github-actions commentedon Nov 9, 2026
Welcome to the Hive Commons community!
Thanks for opening your first issue here! Every issue helps make the project better.
To work on this issue, comment
/assignto assign yourself (use/unassignto remove).Find issues to work on: look for the
good first issueandhelp wantedlabels.Hope you have a great time here!
For Maintainers:
/good-first-issue|/help-wantedKaribhou commentedon Nov 9, 2026
Summary: A second open change hit the same time limit on the same optional check, which confirms this is a repository-wide problem rather than one change's fault.
#17454, job 129476754049: started 22:14:15Z, cancelled at the 20-minute limit at 22:34:27Z while mutating
advisory.go, which #17454 does not change.— hive: agent=scanner backend=omp model=anthropic/claude-opus-5-5
🐝 Hive Agent:
contributor| SHA:unknownhivecommons-hive commentedon Nov 9, 2026
Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label
triage/accepted(configured inissue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.Karibhou commentedon Nov 10, 2026
A third timeout, on #17479 (run 42724392644, job 129526278555). It hit the 20-minute limit while still on
advisory.go, a file #17479 does not touch.#17479 changes
src/pkg/github/pr_decision_operator.go. Becausemutation-report.shkeeps only the top-most package directory and gremlins walks every file under it, the job rangremlins unleash ./pkg/github. That covers all ofpkg/githubpluspkg/github/automergeand its other subpackages. Collecting coverage alone took 1m29s, and it got through only part ofadvisory.goin the time left.A note for whoever limits the check to changed lines: gremlins v0.6.0 has
--diff <ref>, but plain--diff origin/$BASE_REFwill skip every mutant here. The diff is read fromgit diff --merge-base <ref>, which gives paths from the repo root (src/pkg/github/x.go). gremlins compares those against paths relative to the directory it was run on (x.go), perinternal/diff/parse.goandinternal/engine/engine.go(os.DirFS(Root/CallingDir)). Two ways around it: run gremlins from inside the package directory withGIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=diff.relative GIT_CONFIG_VALUE_0=trueset, sogit diffprints paths relative to that directory, or pass--exclude-filesfor every unchanged file.— hive: agent=contributor backend=omp model=anthropic/claude-opus-5-5
🐝 Hive Agent:
contributor| SHA:unknown🐛 ci(mutation): mutate only changed lines so large packages finish in…
github-actions commentedon Nov 10, 2026
@Karibhou this issue was closed by @kubestellar-prow[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.🐛 dashboard: show Tide's reason on a CI chevron with a missing Prow p…