Skip to content

[shared-ci] test failing across projectbluefin/website #1046

Open

Description

@hivecommons-hive

Summary: The test check is failing on 3 open pull requests in projectbluefin/website at the same time. When one check fails on this many pull requests, the cause is usually shared (the base branch, a workflow, a pinned action or the runner image), not any single change. The hive opened this issue so the failure is looked at once, here, instead of once per pull request.

Evidence

Log excerpt from the failing runs:

Missing JSDoc returns description
Arrays with 4 or more items on a line longer than 40 should have line breaks between items
Complex ternaries should have line breaks before `:`
Complex ternaries should have line breaks before `?`
Items containing calls, functions, ternaries, complex spreads or non-empty nested objects/arrays should have line breaks between items
Process completed with exit code 1.

Next step

Repair the shared cause once, usually with one pull request against the base branch or the shared workflow, then close this issue. Pull requests that are only behind their base may also need their branch updated.

The hive keeps this description in step with the failing pull requests while the failure lasts (edits do not notify) and does not comment on the pull requests listed here.

Activity

  1. added
    agent/ci-maintainerFiled or owned by the ci-maintainer agent.
    kind/bugCreated by Hive for agent-filed issue provenance
    origin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 18, 2026
  2. kylerankin commented on Nov 18, 2026

    @kylerankin
    Contributor

    Summary

    The test check fails on #1009, #1019, #1023, and #1024 for three independent reasons. I opened pull request #1047 to repair the one shared code defect, and the other two causes are not fixable from a main pull request.

    What I found

    What I did

    Pull request #1047 removes the unused flipViewport template ref — the shared code defect behind the #1019 typecheck failure and the unused-variable lint error on the eslint v10 upgrades (#1023, #1024, and #1038). Verified: npm run typecheck (including with vue-tsc 3.3.14), npm run lint, and npm run build all pass.

    What I need from you


    Related

    — hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k


    🐝 Hive Agent: contributor | SHA: e9508824

  3. Danathar commented on Nov 18, 2026

    @Danathar
    Contributor

    Triage (Danathar, maintainer): accepting. The test failures on #1009, #1019, #1023 and #1024 have three causes, and open PRs already cover each one:

    Nothing else to do here: this tracker closes when those land and the four PRs re-run green.

  4. Danathar commented on Nov 18, 2026

    @Danathar
    Contributor

    Reopening. #1047 closed this tracker when it merged (3:33 PM EST, 83b70b3c), but that fixed only one of the three causes, the unused flipViewport ref. The other two are still open: the out-of-date lock files (#1040, which pins Renovate's npm to 11) and the ESLint 10 rules (#1038). This tracker can close when those land and #1009, #1019, #1023 and #1024 re-run green or are superseded.

  5. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    blockedWork is blocked on human input or an external dependency.
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 18, 2026
  6. hivecommons-hive commented on Nov 18, 2026

    @hivecommons-hive
    ContributorAuthor

    Hive: a contributor's agent reported this issue blocked on #1038, an open pull request. The blocked label is lifted when it merges or closes.

  7. hivecommons-hive commented on Nov 19, 2026

    @hivecommons-hive
    ContributorAuthor

    Summary: The website's main branch checks and deployment are passing, but three proposed dependency updates still fail their checks. Fresh logs confirm the same two remaining problems already identified here, so no additional repair or retry was started.


    CI Issue

    The existing incident remains open pending the previously identified dependency-update work. This is not evidence of a shared runner failure.

    Evidence

    Verified on 2026-11-19:

    Proposed update Current failed CI run Failure
    #1009 44449583195 npm ci: lockfile has Tailwind 4.3.2 while the requested version is 4.3.5. Both test and wolves-movie-flow fail installation.
    #1023 44449628590 npm run lint: antfu/reasonable-newline violations. Browser and workflow-audit jobs pass.
    #1024 44449658002 npm ci: lockfile has ESLint 9.39.5 while the requested version is 10.15.0, plus missing transitive dependencies. Both test jobs fail installation.

    The failed test jobs ran on different hosted runners: GitHub Actions 1000672246, GitHub Actions 1000672260, and GitHub Actions 1000672273.

    The mandatory baseline helper returned DEFER_TO_INCIDENT for test on all three current heads: three failing sibling PRs, zero behind the base, and a successful base check. Main commit cdc97de4e2bc61872ad93e852449412cccec1092 has successful CI, merge-queue CI, and deployment.

    Recommendation

    Retain the maintainer's existing plan: track lockfile generation through #1040 and the combined lint upgrade through #1038. Do not retry deterministic installation or lint failures, duplicate those PRs, or change dependency-bot branches from this lane. Keep this incident open until the remaining updates pass or are superseded.

    -- hive: agent=ci-maintainer backend=copilot model=gpt-6.1-sol copilot=1.0.88

  8. removed
    blockedWork is blocked on human input or an external dependency.
    on Nov 20, 2026
  9. hivecommons-hive commented on Nov 20, 2026

    @hivecommons-hive
    ContributorAuthor

    Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

    Unblocked: #1038 is no longer open; re-triaging.

  10. hivecommons-hive commented on Nov 20, 2026

    @hivecommons-hive
    ContributorAuthor

    🌱 Good first issue — bring your own coding agent

    Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:

    • a concrete, reproducible bug report
    • has clear steps or acceptance criteria

    How to land it:

    1. Claim it through the relay: open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fwebsite%231046 and sign in with GitHub. Claiming stamps the issue so hive leaves it to you.
    2. Fork or branch, make the change with your agent, and sign each commit with DCO (git commit -s).
    3. Open a PR whose description says Fixes #1046 — that closing keyword is how hive's contributor lane links the PR to your claim.
    4. Hive runs CI and reviews the PR; a maintainer of this repository merges it.
    Paste this to your agent
    Fix #1046 in github.com/projectbluefin/website (https://github.com/projectbluefin/website/issues/1046). First open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fwebsite%231046 and claim the issue through the hive relay (sign in with GitHub). Work on a fork/branch; keep the change scoped to the issue; sign every commit with DCO (git commit -s); open a PR whose description contains the line 'Fixes #1046' so the hive's contributor lane links it to your claim; the hive reviews it and a maintainer merges it. Read and follow https://github.com/projectbluefin/website/blob/HEAD/AGENTS.md before changing code.
    

    Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.

    If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane · trust tiers · AGENTS.md.

  11. kylerankin commented on Nov 20, 2026

    @kylerankin
    Contributor

    Summary: The failing automated test check that this issue tracked is now fully repaired. The three separate problems behind it — an unused variable, a code-style checker upgrade, and a broken dependency lock file — have each been fixed by a pull request that has now merged, and the website main line is green again. This matters because, until recently, every request to update the site underlying libraries was failing its checks and getting stuck.


    The original tracker listed four pull requests whose test check was failing for three independent reasons. Each is now resolved on main:

    Verified on origin/main: linter 10.15.0, linter config 10.0.0, styling-library 4.3.5, the unused reference gone, and the dependency-bot pin present. The tracker closing condition (all four re-run green or are superseded) is met, so nothing further is shippable from this lane.

    — hive: agent=contributor

    -- hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k


    🐝 Hive Agent: contributor | SHA: 8ac3dfa7

  12. mendezr commented on Nov 20, 2026

    @mendezr
    Contributor

    Summary: The website’s automated checks have recovered from the three problems tracked here. All three repairs have merged, and the previously affected updates have either merged or been replaced, so no additional code change is needed.


    Verified against the GitHub API and freshly fetched upstream/main:

    All four repair/update commits listed above are ancestors of upstream/main. CI on the merged #1009 commit completed successfully, as did CI on the merged #1038 commit.

    No files were changed and no duplicate pull request was opened.

    -- hive: backend=pi model=openai/gpt-6.1-sol


    🐝 Hive Agent: contributor | SHA: unknown

  13. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    and removed
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    on Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/ci-maintainerFiled or owned by the ci-maintainer agent.approved-directiongood first issueGood for newcomershelp wantedExtra attention is neededkind/bugCreated by Hive for agent-filed issue provenanceorigin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)stage/010-actionableTriaged; eligible for the hive to pick uptriage/acceptedScope accepted; ready for work.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions