WIP: fix(ci): Don't cache nix store #1047

Draft

Shuroii wants to merge 1 commit from Shuroii/continuwuity:flake-updater into main

pull from: Shuroii/continuwuity:flake-updater

merge into: continuwuation:main

continuwuation:main

continuwuation:renovate/lock-file-maintenance

continuwuation:renovate/rand-0.x

continuwuation:renovate/opentelemetry-rust-monorepo

continuwuation:renovate/axum-monorepo

continuwuation:jade/flake-clone

continuwuation:nex/fix/event-auth

continuwuation:renovate/rust-patch-updates

continuwuation:ginger/upload-rpms-on-schedule

continuwuation:nex/fix/incoming-fetch

continuwuation:nex/fix/upgrade

continuwuation:tom/ci-fedora-rpm

continuwuation:nex/fed-improvements

continuwuation:jade/ci-release-fix

continuwuation:jade/rocksdb-10-5

continuwuation:illegal-car-mods

continuwuation:ginger/fix-msc4133-migration

continuwuation:ginger/migrate-busted-tz

continuwuation:hydra/public

continuwuation:tom/max-perf-docs

continuwuation:nex/feat/manual-extremities

continuwuation:nex/feat/async-media

continuwuation:nex/feat/fast-joins-hack-do-not-use-DO-NOT-USE

continuwuation:nex/feat/better-logging

continuwuation:trigger-ci-so-latest-isnt-on-illegal-car-mods

continuwuation:nex/feat/pins-backfill

continuwuation:jade/tuwunel-2025-06-old

continuwuation:jade/ai-slop-db-docs

continuwuation:nex/fix-create-auth

continuwuation:jade/version-stats

continuwuation:jade/read-receipts

continuwuation:dahsa_uwu/axum-0.8

continuwuation:jade/rust-toolchain-no-targets

continuwuation:jade/logging-features

continuwuation:jade/syncv5-typing

continuwuation:jade/msc2815

continuwuation:jade/relations

continuwuation:jade/purge-sync-tokens

continuwuation:morguldir/see-eye

continuwuation:jade/css-small-screen

continuwuation:nex/wip-751

continuwuation:tuwunel-rebase

continuwuation:test

continuwuation:oddlid/rename-admin-room-bot

continuwuation:strawberry/nix-ci-stuff

continuwuation:strawberry/valgrind

continuwuation:strawberry/morgs-snake-sync-jason-main

continuwuation:newer-media-endpoints

continuwuation:folly-coroutines-async-io

continuwuation:federation-retry-timer-port

continuwuation:bad-attempt-at-extracting-homeserver-signing-key

continuwuation:room-deletion-attempt-do-not-use

Conversation 8 Commits 1 Files changed 1 +6 -7

Shuroii commented 2025-09-18 22:30:21 +00:00

Contributor

Copy link

Tom should look at this later.

Tom should look at this later.

Shuroii commented 2025-09-18 22:33:40 +00:00

Author

Contributor

Copy link

That's weird; 7a56a2462c didn't apply and Forgejo doesn't seem to care?

That's weird; 7a56a2462c5cacb2361fd39879245fed63ffb630 didn't apply and Forgejo doesn't seem to care?

Shuroii force-pushed flake-updater from a5f2e5f389 to 6a33fcb63d 2025-09-18 22:34:45 +00:00 Compare

Shuroii force-pushed flake-updater from 6a33fcb63d to fbeac33487 2025-09-18 22:40:56 +00:00 Compare

tcpipuk commented 2025-09-18 22:49:08 +00:00

Owner

Copy link

Could you explain the reasoning behind the PR?

Could you explain the reasoning behind the PR?

Shuroii changed title from fix(ci): Don't cache nix store to WIP: fix(ci): Don't cache nix store 2025-09-18 22:50:40 +00:00

Shuroii commented 2025-09-18 22:51:16 +00:00

Author

Contributor

Copy link

@tcpipuk wrote in #1047 (comment):

Could you explain the reasoning behind the PR?

https://forgejo.ellis.link/continuwuation/continuwuity/actions/runs/5058/jobs/0/attempt/1 shows the workflow broke cause of something to do with caching.

@tcpipuk wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/1047#issuecomment-20322: > Could you explain the reasoning behind the PR? https://forgejo.ellis.link/continuwuation/continuwuity/actions/runs/5058/jobs/0/attempt/1 shows the workflow broke cause of something to do with caching.

Shuroii force-pushed flake-updater from fbeac33487 to 955c262884 2025-09-18 22:54:02 +00:00 Compare

tcpipuk commented 2025-09-18 22:56:02 +00:00

Owner

Copy link

Does it? To me, it shows the end of a bunch of actions then shows the job failed, but I don't see any logs indicating cache at all?

Does it? To me, it shows the end of a bunch of actions then shows the job failed, but I don't see any logs indicating cache at all?

Shuroii commented 2025-09-18 22:58:27 +00:00

Author

Contributor

Copy link

On line 2 of the "Complete job" step, it mentions this command: docker cp src=/data/.cache/act/f4/1cef77644f38300adc245bd8163db2c0e1de5f17a02e3a3515052350c1c43d/ dst=/var/run/act/actions/f4/1cef77644f38300adc245bd8163db2c0e1de5f17a02e3a3515052350c1c43d/ but the UI doesn't mention if this command fails correctly or not. That said, it's the only thing that can fail, unless we've got another excellent Forgejo runner error report issue on our hands.

On line 2 of the "Complete job" step, it mentions this command: `docker cp src=/data/.cache/act/f4/1cef77644f38300adc245bd8163db2c0e1de5f17a02e3a3515052350c1c43d/ dst=/var/run/act/actions/f4/1cef77644f38300adc245bd8163db2c0e1de5f17a02e3a3515052350c1c43d/` but the UI doesn't mention if this command fails correctly or not. That said, it's the only thing that *can* fail, unless we've got another excellent Forgejo runner error report issue on our hands.

Shuroii force-pushed flake-updater from 955c262884 to e012843898 2025-09-18 23:21:57 +00:00 Compare

Shuroii force-pushed flake-updater from e012843898 to 07fd83cefc 2025-09-18 23:28:29 +00:00 Compare

tcpipuk commented 2025-09-19 10:46:26 +00:00

Owner

Copy link

AFAICT, there's nothing in the workflow that causes the nix store to be cached.

I think we'd get an error if that copy failed, but if that nix action was trying to copy data to /var/run/act/ then that probably failed because the runner is in Docker (that path doesn't exist on the host) so sounds like that action might be making assumptions about the environment...

In either case, the latest failure suggests the problem is trying to push to a branch that doesn't exist on the upstream.

AFAICT, there's nothing in the workflow that causes the nix store to be cached. I think we'd get an error if that copy failed, but if that nix action *was* trying to copy data to `/var/run/act/` then that probably failed because the runner is in Docker (that path doesn't exist on the host) so sounds like that action might be making assumptions about the environment... In either case, the [latest failure](https://forgejo.ellis.link/continuwuation/continuwuity/actions/runs/5090/jobs/0) suggests the problem is trying to push to a branch that doesn't exist on the upstream.

nyanbinary commented 2025-09-21 02:03:44 +00:00

Contributor

Copy link

The flake can be bumped manually for now right, to fix the rocksdb version.

The flake can be bumped manually for now right, to fix the rocksdb version.

nyanbinary commented 2025-09-23 02:12:09 +00:00

Contributor

Copy link

https://github.com/samueldr/lix-gha-installer-action
https://git.madhouse-project.org/actions
Might be interesting to use as well :p

https://github.com/samueldr/lix-gha-installer-action https://git.madhouse-project.org/actions Might be interesting to use as well :p

Some checks failed

Hide all checks

Documentation / Build and Deploy Documentation (pull_request) Has been skipped

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m17s

Required

Details

Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 2m58s

Required

Details

Update flake hashes / update-flake-hashes (pull_request) Failing after 10s

Details

Release Docker Image / Build linux-amd64 (release) (pull_request) Successful in 4m26s

Details

Release Docker Image / Build linux-arm64 (release) (pull_request) Successful in 4m36s

Details

Release Docker Image / Create Multi-arch Release Manifest (pull_request) Successful in 4s

Details

Release Docker Image / Build linux-amd64 (max-perf) (pull_request) Successful in 20m12s

Details

Release Docker Image / Build linux-arm64 (max-perf) (pull_request) Successful in 20m53s

Details

Release Docker Image / Create Max-Perf Manifest (pull_request) Successful in 4s

Details

This pull request has changes conflicting with the target branch.

• .forgejo/workflows/update-flake-hashes.yml

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u flake-updater:Shuroii-flake-updater

git switch Shuroii-flake-updater

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

Bug

Something isn't working as intended

  

Cherry-picking

Commits picked from other conduit projects

  

Database

This requires or includes changes to the database

  

Dependencies

Something dependency related

  

Dependencies/Renovate

Automatic dependency upgrades by Renovate

  

Difficulty

Easy

Low difficulty to implement - touches few parts of the codebase, low complexity

  

Difficulty

Hard

High difficulty to implement - touches many parts of the codebase, high complexity

  

Difficulty

Medium

Medium difficulty to implement - touches more parts of the codebase, higher complexity

  

Documentation

Improvements or additions to documentation

  

Enhancement

New feature or request

  

Good first issue

Good for newcomers

  

Help wanted

Additional eyes and keyboards are required for this one

  

Inherited

Issues that have been inhereted from the project pre-fork

  

Matrix/Administration

Features pertaining to homeserver administration

  

Matrix/Appservices

Features pertaining to the appservice API

  

Matrix/Auth

Features pertaining to authentication

  

Matrix/Client

Features pertaining to client-to-server interactions

  

Matrix/Core

Issues relating to core matrix functionality, such as state resolution and PDU formats

  

Matrix/Federation

Features pertaining to server-to-server interactions

  

Matrix/Hydra

Issues related to room version 12 and related changes (temporary label)

  

Matrix/MSC

Features pertaining to unstable matrix features

  

Matrix/Media

Features pertaining to media interactions

  

Meta

Related to housekeeping, maintenance, or other repo-meta.

  

Meta/CI

Issues related to CI changes

  

Meta/Packaging

Packaging

  

Priority

Blocking

This issue is blocking the next release

  

Priority

High

This issue is very important

  

Priority

Low

This issue is of a rather low priority

  

Security

This item is related to general security

  

Status/Blocked

This pull request or issue is currently blocked from being merged/closed

  

Status

Confirmed

This issue has enough information and is confirmed

  

Status

Duplicate

This issue or pull request already exists

  

Status

Invalid

This issue doesn't seem right

  

Status

Needs Investigation

This issue needs further investigation

  

To-Merge

  

Wont fix

This will not be worked on

  

old/ci/cd

Ci/CD

Archived

  

old/rust

Pull requests that update Rust code

Archived

No labels

Bug

Cherry-picking

Database

Dependencies

Dependencies/Renovate

Difficulty

Easy

Difficulty

Hard

Difficulty

Medium

Documentation

Enhancement

Good first issue

Help wanted

Inherited

Matrix/Administration

Matrix/Appservices

Matrix/Auth

Matrix/Client

Matrix/Core

Matrix/Federation

Matrix/Hydra

Matrix/MSC

Matrix/Media

Meta

Meta/CI

Meta/Packaging

Priority

Blocking

Priority

High

Priority

Low

Security

Status/Blocked

Status

Confirmed

Status

Duplicate

Status

Invalid

Status

Needs Investigation

To-Merge

Wont fix

old/ci/cd

old/rust

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Notifications

Subscribe

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

continuwuation/continuwuity!1047

No description provided.