ci: CircleCI's setup-main stays pending on every main commit since Nov 15 17:57 UTC, so no checks run and no gate posts #1412
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1412
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@drcrow: since 17:57 UTC on Nov 15, CircleCI's setup job has stayed pending on every
maincommit. It never starts, so no checks run andmb/gateposts nothing. I have no CircleCI access, so this is what Forgejo's commit statuses show. The cause is a guess for someone who can open the CircleCI org to confirm.What the statuses show
deb9f781, Nov 15 17:25 UTC),ci/circleci: setup-mainwent pending, then success a minute later, and the continued workflow posted lint, third-party, test-linux, guide-screenshots, website, spirv-fixtures, windows-builder and windows-vulkan. Seven moremaincommits did the same, the last oneb7a014b8(17:52:55 UTC).1576a274(17:57:35 UTC) and on everymaincommit since, through544229a2(Nov 17 03:50 UTC),setup-mainis postedpendingby circleci-bot with a workflow link, and nothing follows. I checked the first 40 commits after #417 one by one, then sampled every fourth up to today: 55 pending and none finished afterb7a014b8.ci/circleci: setup-noop-tagandsetup-releasestay pending on the nightly-tagged commits.b7a014b8..1576a274touches no file under.circleci/, and neither does any later commit. The config is the one that worked eight times in a row.Example on today's head
544229a2:ci/circleci: setup-mainpending since 2026-11-17T03:50:23Z, https://app.circleci.com/workflow/dec97c4c-183f-403b-9016-6393817f08d0/job/b9dd9a65-b3b2-4c8c-8fe8-759afcdd9d38Likely cause (not confirmed)
mb/setup(Orbsrc/jobs/setup.yml) runs on CircleCI's cloud Docker,cimg/basesmall, not a self-hosted runner, so no runner of ours can be offline. A cloud job queued forever usually means the organisation can't start jobs: monthly credits used up, a spend limit, or a concurrency cap. It stopped about 30 minutes after cutover. In that time eight fullmainpipelines ran (force-full: true: large Docker jobs, an ARM job and the Windows machine jobs), so used-up credits is my first guess.What would confirm or fix it
main, only run the full set whennightlyneeds it (or on a schedule), and leave the per-commit run to the path areas. Pull requests already work that way.mainisn't unguarded, but the CircleCI gate never reports, and #1145's description of CI is ahead of what runs.Found during a red-main sweep. The game-free failures on
mainare a separate problem, being fixed in #1323, #1363, #1409 and #1410.