!PbtOpdWBSRFbEZRLIf:numtide.com

Nix Community Projects

663 Members
Meta discussions related to https://nix-community.org. (For project specific discussions use github issues or projects own matrix channel). Need help from an admin? Open an issue on https://github.com/nix-community/infra/issues166 Servers

Load older messages


SenderMessageTime
8 Oct 2021
@colemickens:matrix.orgcolemickens 🏳️‍🌈 I'm using flakes, I know the outpath and drvs I'm dealing with 07:43:15
@colemickens:matrix.orgcolemickens 🏳️‍🌈like, for a fact.07:43:17
@zimbatm:numtide.comJonas Chevalier if it changes, it's usually a purity issue, like when src = ./. is being used 07:43:17
@colemickens:matrix.orgcolemickens 🏳️‍🌈this isn't a purity or eval mismatch thing07:43:30
@colemickens:matrix.orgcolemickens 🏳️‍🌈 I think the problem is that I'm telling nix-build not to build during the dry-run, and that's causing issues because the drvs themselves aren't cached 07:44:27
@colemickens:matrix.orgcolemickens 🏳️‍🌈as soon as I make the "in between" drvs available, or let nix-build --dry-run do some building, it acts like I'd expect.07:44:53
@colemickens:matrix.orgcolemickens 🏳️‍🌈turns out the hack isn't hacky enough07:45:00
@zimbatm:numtide.comJonas Chevalier if you're using nix-build then it's not using the pure eval that flake guarantees 07:45:20
@colemickens:matrix.orgcolemickens 🏳️‍🌈sorry this isn't going anywhere07:45:35
@colemickens:matrix.orgcolemickens 🏳️‍🌈 I know what I'm doing, I've spent extensive, exhaustive time with this. nix-build is evaluating and building the same derivations. 07:46:05
@colemickens:matrix.orgcolemickens 🏳️‍🌈as in, literally teh second the drvs were available, nix-build-uncached and nix-build spat out the same out path ad started pulling the (same) out path from the cache07:46:48
@zimbatm:numtide.comJonas ChevalierI don't have access to your machine or your brain, all I can do is probe through you07:47:21
@colemickens:matrix.orgcolemickens 🏳️‍🌈sure but I'm telling you that I'm specifically only using known drv and out paths on the secondary test machine. there's literally no risk that its something as simple as mis-eval07:47:55
@colemickens:matrix.orgcolemickens 🏳️‍🌈anyway, I think I figured out the issue, I need to be more forceful about having cachix push drvs up to get the behavior I want07:48:16
@zimbatm:numtide.comJonas Chevalierthe number of times I heard that, and then the person is like: opps :p07:48:28
@zimbatm:numtide.comJonas Chevalier nix-build --store is not reliable, I think it needs to have write access to the store to work as expected, which wouldn't work with cachix. 07:53:14
@colemickens:matrix.orgcolemickens 🏳️‍🌈yeah, :P I really don't quite understand how it's meant to be used for that scenario anyway. I guess my assumption was that they've made it so that it will notice the store being readonly and fallback to the "auto" worker? seems like the "auto" keyword has been getting some work?07:56:09
@colemickens:matrix.orgcolemickens 🏳️‍🌈(otherwise I'm not sure why it was at all suggested as a solution? not to be dismissive of the work, I assume I just don't understand)07:56:47
@colemickens:matrix.orgcolemickens 🏳️‍🌈 * (otherwise I'm not sure why it was at all suggested as a solution on that Issue? not to be dismissive of the work, I assume I just don't understand)07:56:56
@mic92:nixos.devMic92Personally I moved on to hydra, in cases I would have need nix-build-uncached. I would pick it up, I would go for https://github.com/nix-community/nix-eval-jobs which is faster due to use of threads.09:15:18
@mic92:nixos.devMic92I only use it for my nur-packages09:15:54
@mic92:nixos.devMic92I am actually trying to make hydra more accessible: https://github.com/NixOS/hydra/pull/103309:16:11
@mic92:nixos.devMic92Once you have documentation on how to declarative add jobsets it's probably the fastest way to evaluate nix projects.09:17:05
@mic92:nixos.devMic92And than there is hercules if you want better github integration09:17:44
@fedx:matrix.orgfedx joined the room.15:20:21
9 Oct 2021
@colemickens:matrix.orgcolemickens 🏳️‍🌈I like to dream about something better.00:28:30
@colemickens:matrix.orgcolemickens 🏳️‍🌈a CI system that knew about flake inputs, knew about upstreams for the flake inputs, knew about "upgrade groups" of flake inputs -> it could list outputs, update all inputs in an "upgrade group", relist outputs, build the new outputs, move on to next upgrade group. You could have rich data about your flake input upgrades over time, you could have a smarter flake upgrade process than I've seen anyone implement so far...00:30:13
@colemickens:matrix.orgcolemickens 🏳️‍🌈that doc pr is great too00:30:18
@colemickens:matrix.orgcolemickens 🏳️‍🌈I had actually done all this once, I even have scripts that wipe/resetup hydra/rePOST my initial declarative job, etc.00:30:42
@colemickens:matrix.orgcolemickens 🏳️‍🌈But I don't like hydra.00:30:45

Show newer messages


Back to Room ListRoom Version: 6