This website requires JavaScript.
Explore
Help
Sign in
max
/
nix-super
Watch
1
Star
0
Fork
You've already forked nix-super
0
mirror of
https://github.com/privatevoid-net/nix-super.git
synced
2024-12-05 03:46:16 +02:00
Code
Issues
Projects
Releases
Packages
Wiki
Activity
Actions
1
a7b1b92d81
nix-super
/
tests
/
build-hook-ca-floating.nix
7 lines
88 B
Nix
Raw
Normal View
History
Unescape
Escape
Test remote building with fixed output derivations
2020-08-16 20:38:12 +03:00
{
busybox
}:
Fix `nix log` with CA derivations Fix #6209 When trying to run `nix log <installable>`, try first to resolve the derivation pointed to by `<installable>` as it is the resolved one that holds the build log. This has a couple of shortcomings: 1. It’s expensive as it requires re-reading the derivation 2. It’s brittle because if the derivation doesn’t exist anymore or can’t be resolved (which is the case if any one of its build inputs is missing), then we can’t access the log anymore However, I don’t think we can do better (at least not right now). The alternatives I see are: 1. Copy the build log for the un-resolved derivation. But that means a lot of duplication 2. Store the results of the resolving in the db. Which might be the best long-term solution, but leads to a whole new class of potential issues.
2022-03-08 07:02:25 +02:00
import
./build-hook.nix
{
inherit
busybox
;
contentAddressed
=
true
;
}
Reference in a new issue
Copy permalink