!zghijEASpYQWYFzriI:nixos.org

Hydra

343 Members
99 Servers

Load older messages

SenderMessageTime
19 Mar 2024
@elvishjerricco:matrix.orgElvishJerricco yea, even the build in my hydra is 1.6G, which is unexpectedly slightly smaller, but more importantly still below the default max_output_size of 2 << 30 17:27:43
@elvishjerricco:matrix.orgElvishJerricco I guess we'll see if increasing max_output_size to 16G does the trick 17:29:09
@casey:hubns.net@casey:hubns.neti also ran into hijinx with auto-optimise-store with reporting output sizes, if you have that enabled. though, iirc, that was with disk image projected size rather than general outputs. or if you might be running a compressed fs17:40:10
@elvishjerricco:matrix.orgElvishJerricco cransom: hm that might be confusing things 17:52:26
@elvishjerricco:matrix.orgElvishJerriccohard to say17:52:30
@elvishjerricco:matrix.orgElvishJerriccodammit I still got the output limit error20:16:42
@elvishjerricco:matrix.orgElvishJerriccodoes it cache the error, regardless of if the conf conditions change?20:17:13
@elvishjerricco:matrix.orgElvishJerriccohow could I fix that?20:17:18
@elvishjerricco:matrix.orgElvishJerriccofuck I'm going to build on staging aren't I20:17:54
@ma27:nicht-so.sexyma27 aren't failures cached (as well as successes) in Hydra as long as the drv doesn't change?
not sure what you're up to, but the cheapest trick is probably to just add another env var to the drv to force a rebuild. 		21:06:18
@linus:schreibt.jetzt@linus:schreibt.jetzt
In reply to @ma27:nicht-so.sexy
IIRC it was increased for ghc in the past already?
Specifically for GHC on ARM, if I'm remembering right, because it's much bigger for reasons 		21:50:02
@bumperboat:matrix.orgbumperboat set a profile picture.22:20:52
20 Mar 2024
@rick:matrix.ciphernetics.nl@rick:matrix.ciphernetics.nlhttps://github.com/NixOS/nixpkgs/pull/297392, would be great if someone could check what's going wrong here, haven't looked very deeply. But hydra seems to be running fine on my end with that change.09:24:50
@lotte:chir.rs@lotte:chir.rs changed their profile picture.11:03:24
21 Mar 2024
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.18:02:54
@grahamc:nixos.org@grahamc:nixos.org left the room.20:09:46
22 Mar 2024
@bumperboat:matrix.orgbumperboat changed their display name from bumperboat to bumperboat (UTC+8 when).13:27:55
@bumperboat:matrix.orgbumperboat changed their display name from bumperboat (UTC+8 when) to bumperboat (UTC+8).15:01:25
24 Mar 2024
@belak:matrix.org@belak:matrix.org joined the room.18:24:50
@darkwater4213:matrix.orgdarkwater4213How feasible is self-hosting a Hydra instance? Say I want to deploy to a whole bunch of RISC-V thin clients... I already know what packages I want to be compiled, so is there a way to configure Hydra to only build and serve those? Or am I fundamentally messengering something about Hydra?21:51:50
@casey:hubns.net@casey:hubns.netself hosting hydra is easy. it's probably over kill if you are only intending it to populate a binary cache though.23:15:35
25 Mar 2024
@darkwater4213:matrix.orgdarkwater4213For RISC-V? Does the main instance of Hydra compile for RISC-V?01:35:59
@darkwater4213:matrix.orgdarkwater4213Or ARM?01:36:08
@k900:0upti.meK900
In reply to @darkwater4213:matrix.org
For RISC-V? Does the main instance of Hydra compile for RISC-V?
It doesn't really matter for what, it just does normal Nix remote builds 		05:11:45
@k900:0upti.meK900 hydra.n.o doesn't build RISCV because we don't have the hardware for it 05:12:01
@rick:matrix.ciphernetics.nl@rick:matrix.ciphernetics.nl
In reply to @darkwater4213:matrix.org
How feasible is self-hosting a Hydra instance? Say I want to deploy to a whole bunch of RISC-V thin clients... I already know what packages I want to be compiled, so is there a way to configure Hydra to only build and serve those? Or am I fundamentally messengering something about Hydra?
With nixpkgs or the flake it's easy to host, providing you're running nixos or don't mind running a VM with nixos. There's definitely a way to configure hydra to build a specific set of packages, that's what it's built to do. I wouldn't really say it's overkill, it's a convenient way to keep up to date with nixpkgs and building what you need from it for what platform you want 		08:37:03
27 Mar 2024
@admin:nixos.org@admin:nixos.org joined the room.13:25:28
Room Avatar Renderer.13:25:56
@admin:nixos.org@admin:nixos.org left the room.13:26:01
30 Mar 2024
@magic_rb:matrix.redalder.orgmagic_rb

i seem to be having issues with hydra not serving static files

4#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/js/jquery/jquery-ui-1.10.4.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/jquery/jquery-ui-1.10.4.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client:, server: hydra.redalder.org, request: "GET /static/js/moment/moment-2.24.0.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/moment/moment-2.24.0.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/fontawesome/css/all.css HTTP/2.0", upstream: "http://127.0.0.1:8666/static/fontawesome/css/all.css", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/js/popper.min.js HTTP/2.0", upstream: "http://127.0.0.1:8666/static/js/popper.min.js", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/css/tree.css HTTP/2.0", upstream: "http://127.0.0.1:8666/static/css/tree.css", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:30 [error] 124#124: *13849359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: , server: hydra.redalder.org, request: "GET /static/images/emojione-check-2714.svg HTTP/2.0", upstream: "http://127.0.0.1:8666/static/images/emojione-check-2714.svg", host: "hydra.redalder.org", referrer: "https://hydra.redalder.org/project/dotfiles"
2024/03/30 21:26:33 [warn] 125

this is from a nginx remote proxy, in the browser the page just times out

20:30:19

Show newer messages

Back to Room ListRoom Version: 6