worldofpeace changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS 20.09 Nightingale ✨ https://discourse.nixos.org/t/nixos-20-09-release/9668 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.09 RMs: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
bpye has quit [Ping timeout: 240 seconds]
bpye has joined #nixos-dev
<ekleog> Hmm… is there an estimation of how much RAM nixpkgs-review needs for eval somewhere? IIRC it already has mechanisms to limit the runtime, but I'd be interested in a rough estimate of the amount of RAM required to successfully just run nixpkgs-review
<ekleog> oh actually looks like it went down and I can now run it on my machine, so the answer to myself is 5G
<rmcgibbo[m]> ekleog: It depends on whether you're reviewing a PR that OfBorg has evaluated the changed attrs of or not.
<rmcgibbo[m]> If so, then you don't need much RAM since you don't need to `nix-env -qaP`. If `nixpkgs-review` needs to run `nix-env -qaP` itself to identify the changed attrs, then yeah... >4G
<ekleog> rmcgibbo[m]: right, here I'm considering the point of view of someone running nixpkgs-review locally before submitting a PR (writing a tool for PR submission as promised in https://github.com/NixOS/nixpkgs/pull/117537 ; so I'm thinking of making the default for “do you want to run nixpkgs-review” be the one that's most likely to work if there's <5-6G of available memory)
<{^_^}> #117537 (by Ekleog, 2 days ago, open): pull request template: cleanup
<ekleog> thank you for your confirmation of >4G needed! :)
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
<supersandro2000> ekleog: you can limit the RAM nix uses with a systemd slice
Synthetica has quit [Quit: Connection closed for inactivity]
ris has quit [Ping timeout: 252 seconds]
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #nixos-dev
mkaito has quit [Quit: WeeChat 3.1]
orivej has quit [Ping timeout: 246 seconds]
cole-h has joined #nixos-dev
maljub01 has joined #nixos-dev
copumpkin has quit [Quit: Hmmm]
kini has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-dev
cole-h has quit [Ping timeout: 260 seconds]
FRidh has joined #nixos-dev
jonringer has quit [Ping timeout: 252 seconds]
rajivr has joined #nixos-dev
evils has joined #nixos-dev
orivej has joined #nixos-dev
__monty__ has joined #nixos-dev
Magic_RB has joined #nixos-dev
ris has joined #nixos-dev
Magic_RB has quit [Killed (Sigyn (Spam is off topic on freenode.))]
Synthetica has joined #nixos-dev
Magic_RB78 has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
mkaito has joined #nixos-dev
mkaito has joined #nixos-dev
copumpkin has joined #nixos-dev
mkaito has quit [Quit: WeeChat 3.1]
<ryantm> Nix isn't compiling on nixpkgs-unstable?
<ryantm> Erp, passing tests*
cole-h has joined #nixos-dev
tomberek has quit [Quit: Ping timeout (120 seconds)]
tomberek has joined #nixos-dev
orivej has joined #nixos-dev
cole-h has quit [Ping timeout: 240 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
Baughn has quit [Read error: Connection reset by peer]
<rmcgibbo[m]> supersandro2000: i've tried to limit the RAM for `nix-env -qaP` with some BOHEMGC_* env variables, and the result is usually just that nix crashes and cannot actually list all of the packages. Does the systemd slice trick actually help it complete the list w/o using lots of ram and w/o crashing?
Baughn has joined #nixos-dev
<supersandro2000> rmcgibbo[m]: I am actually not sure if it works correctly
<supersandro2000> or really hard limit the memory
<supersandro2000> but my system did not freeze due to to high memory usage since I set it up so it must work somehow, right?
<supersandro2000> https://termbin.com/1vgj
orivej has quit [Ping timeout: 246 seconds]
NinjaTrappeur has quit [Quit: WeeChat 3.1]
NinjaTrappeur has joined #nixos-dev
spacekookie has quit [Quit: **aggressive swooshing**]
spacekookie has joined #nixos-dev
spacekookie has quit [Quit: **aggressive swooshing**]
spacekookie has joined #nixos-dev
jonringer has joined #nixos-dev
Baughn has quit [Ping timeout: 260 seconds]
Baughn has joined #nixos-dev
Magic_RB78 has quit [Quit: Connection closed]
FRidh has quit [Quit: Konversation terminated!]
julm has quit [Quit: leaving]
<maralorn> How long until we are allowed to build haskell packages again?
<sterni> at the earliest after we have a unstable channel update with the openssl fix
<sterni> there seem to have been a few build problems today and yesterday, but I haven't been following it closely
<sterni> looks like a lot of aborted jobs? no idea why though
m1cr0man has quit [Quit: G'luck]
julm has joined #nixos-dev
<{^_^}> #117838 (by flungo, 22 minutes ago, open): tor-browser-bundle-bin: 10.0.13 -> 10.0.14
<{^_^}> #117836 (by thyol, 1 hour ago, open): tor-browser-bundle-bin: 10.0.13 -> 10.0.14
<supersandro2000> two first time contributors to the same kind of update in an hour of each other
<sterni> why would it be
<sterni> if the hashes match
<supersandro2000> I don't know. Probably a coincidence
<sterni> tor-browser-bundle-bin is a pretty low hanging fruit as well and it notifies you if it is outdated on startup
<sterni> I think updating tor-browser-bundle-bin was also one of my first contributions
<supersandro2000> 🤔 yeah, probably nothing to think more about
orivej has joined #nixos-dev
evils has quit [Ping timeout: 252 seconds]
cole-h has joined #nixos-dev
__monty__ has quit [Quit: leaving]