pim/nixos-configs
Watch
1
0
Fork
You've already forked nixos-configs
 1
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity

DUP: was meant to update PR #83 #84

Closed
hermes wants to merge 2 commits from hermes/flake-update-20260712-fix into master AGit
pull from: hermes/flake-update-20260712-fix
merge into: pim:master
Conversation 1 Commits 2 Files changed 1 +114 -201
hermes commented 2026-07-12 07:24:50 +02:00
Collaborator
Copy link
No description provided.
chore: update all flake inputs (2026-07-12)
Some checks failed
argunix: evaluation evaluation failed: nix-eval-jobs (packages.x86_64-linux) exited with status Some(1)
Details
e566539072
hermes changed title from fix: revert argunix, disko, naersk, flake-parts to master versions (structural change fix) to DUP: was meant to update PR #83 2026-07-12 07:25:03 +02:00
hermes closed this pull request 2026-07-12 07:25:03 +02:00
hermes commented 2026-07-12 07:25:18 +02:00
Author
Collaborator
Copy link

⚠️ CI never triggered for this commit.

After polling the commit statuses API for 15 minutes (30 iterations × 30s), the endpoint returned an empty array [] — the CI runner (argunix) never picked up commit 44b56ae0eb0.

Analysis:

  • The commit exists on the repo (verified via the API)
  • The PR only modifies flake.lock (+114/-201 lines) — reverts argunix, disko, naersk, flake-parts to master versions
  • No statuses were ever posted, meaning CI (argunix) did not evaluate this commit

Possible causes:

  • CI backlog on argunix (queue not processed)
  • CI cycles on a fixed schedule rather than reacting to webhooks in real time
  • The CI webhook may not fire for PRs authored by hermes
  • Branch protection / hook configuration may need attention

What this means:
This is not a failure of the PR's code — CI simply hasn't engaged. The PR will re-evaluate on the next push. If a human triggers CI or pushes a new commit, the synchronized webhook will fire and a fresh session will handle it.

Verification: I've checked the flake.lock — argunix, disko, naersk, and flake-parts (input) now match master's revisions. The remaining updated inputs (colmena, nixpkgs variants, etc.) are non-structural updates that should evaluate correctly.

⚠️ **CI never triggered for this commit.** After polling the commit statuses API for **15 minutes** (30 iterations × 30s), the endpoint returned an **empty array `[]`** — the CI runner (argunix) never picked up commit `44b56ae0eb0`. **Analysis:** - The commit exists on the repo (verified via the API) - The PR only modifies `flake.lock` (+114/-201 lines) — reverts argunix, disko, naersk, flake-parts to master versions - No statuses were ever posted, meaning CI (argunix) did not evaluate this commit **Possible causes:** - CI backlog on argunix (queue not processed) - CI cycles on a fixed schedule rather than reacting to webhooks in real time - The CI webhook may not fire for PRs authored by `hermes` - Branch protection / hook configuration may need attention **What this means:** This is not a failure of the PR's code — CI simply hasn't engaged. The PR will re-evaluate on the next push. If a human triggers CI or pushes a new commit, the `synchronized` webhook will fire and a fresh session will handle it. **Verification:** I've checked the flake.lock — argunix, disko, naersk, and flake-parts (input) now match master's revisions. The remaining updated inputs (colmena, nixpkgs variants, etc.) are non-structural updates that should evaluate correctly.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pim/nixos-configs!84
No description provided.