worldofpeace_ changed the topic of #nixos-dev to: #nixos-dev NixOS Development (#nixos for questions) | NixOS stable: 20.03 ✨ https://discourse.nixos.org/t/nixos-20-03-release/6785 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 19.09 RMs: disasm, sphalerite; 20.03: worldofpeace, disasm | https://logs.nix.samueldr.com/nixos-dev
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
angerman has quit [Ping timeout: 240 seconds]
alunduil has quit [Ping timeout: 240 seconds]
tom39291 has quit [Ping timeout: 240 seconds]
davidtwco has quit [Ping timeout: 240 seconds]
angerman has joined #nixos-dev
davidtwco has joined #nixos-dev
tom39291 has joined #nixos-dev
alunduil has joined #nixos-dev
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
orivej has quit [Read error: Connection reset by peer]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
<samueldr> hmm :/ the filesystem the build runs on is another ambient impurity which should be tested for reproducible builds
justanotheruser has quit [Ping timeout: 260 seconds]
<gchristensen> :x
<samueldr> $ fallocate -l 8M /nix/store/d5xyf9f8wnj1jl8jmyir47v7dyak1qb4-u-boot-installer-fs.img
<samueldr> fallocate: fallocate failed: Operation not supported
<gchristensen> :x
<samueldr> for this particular issue it looks like it fails the whole build, much better than making a differently-reproduced output
<infinisil> Would using fuse to have a deterministic filesystem layer for builds be possible?
* samueldr thinks about using FAT32 as the filesystem for builds
<gchristensen> or better that reproducible dev FS
<clever> or use disorderfs, and fix the programs to not care
<gchristensen> that one
<infinisil> Tbh fixing programs seems like a neverending struggle
<samueldr> yeah, though disorderfs is for another kind of issue :)
<gchristensen> that is the reproducibility promise!
<samueldr> what I'm seeing is here is features being present *or* lacking
<infinisil> gchristensen: I think making nix-build expose less impurities is much better longterm
<samueldr> the software could be built differently because the feature exists, while still not failing
<samueldr> imagine unicode normalization issues
<infinisil> (though that probably brings other problems with it, such as it being much slower to build stuff..)
<clever> i already had issues with net-snmp, trying to auto-detect what your distro calls /etc/mtab
<qyliss> No way is it possible to maintain a completely reproducible environment forever across all times of machines while still being reasonably performant IMO
<clever> due to the sandbox not including ANY variant, it deduced that the name is "unknown", so it hard-coded itself to just open the literal "unknown" file at runtime, to query it
<qyliss> It's a losing battle
<infinisil> qyliss: Yeah probably, but we should still try to get as close as possible
<samueldr> the issue isn't necessarily to make our builds reproducible by using a filesystem layer, but that *tests* for reproducibility should include that as yet another ambient impurity
<qyliss> infinisil: sure, the more reproducible the environment is, the fewer programs we have to fix
<gchristensen> possibly with tiers, nixos-reproducible, nix-daemon-on-systemd reproducible, single-user-nix reproducible
<samueldr> the first step should be to identify impurity types, list them, and provide guidance?
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
<samueldr> hmm, looks like gnome3.tracker is flaky on aarch64 during its tests https://hydra.nixos.org/job/nixpkgs/trunk/gnome3.tracker.aarch64-linux
<samueldr> on worse performing hardware it fails due to timeouts :/
<samueldr> (in other tests)
<samueldr> 42/43 tracker-sparql-test FAIL 3.11s (exit status 134 or signal 6 SIGABRT)
<samueldr> on the build infra it seems to inconsistently only ABRT on that test
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-dev
<samueldr> started happening with this commit cc jtojnar https://github.com/NixOS/nixpkgs/commit/39b92f6e45534658b49e79c78154df6333af8472
<samueldr> good thing is that makes sense since beforehand it wouldn't test at all
<samueldr> :< the fact that hydra doesn't keep logs for build attempts independently is cramping my style
<samueldr> https://hydra.nixos.org/build/122554337 <- log is of a success, if you follow the propagated build
<samueldr> I wanted to check if it was aarch64 only
<samueldr> so I figure it might have failed at least once?
justanotheruser has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 264 seconds]
orivej_ has joined #nixos-dev
<samueldr> 40/43 miner-monitor FAIL 71.10s (killed by signal 6 SIGABRT)
<samueldr> while running in loop on x86_64-linux, after a good chunk of successful builds
<samueldr> different than the relatively consistent, but not exactly consistent failure on aarch64-linux
orivej_ has quit [Ping timeout: 240 seconds]
<worldofpeace> hmm, maybe I can check if there's something on their issue tracker
<worldofpeace> usually debian is the first to notice stuff like that
<worldofpeace> at most we can just enable them only on x86_64-linux
<samueldr> seems to be way worse for aarch64-linux
<samueldr> but going from failed-but-restarted jobs on hydra, happens too for x86_64-linux
phreedom_ has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
drakonis has quit [Quit: WeeChat 2.8]
dtz has joined #nixos-dev
LnL- has quit [Changing host]
LnL- has joined #nixos-dev
LnL- is now known as LnL
__monty__ has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
alp has joined #nixos-dev
disasm has quit [Ping timeout: 256 seconds]
alp has quit [Ping timeout: 265 seconds]
alp has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
alp has quit [Ping timeout: 240 seconds]
alp has joined #nixos-dev
xwvvvvwx has quit [Quit: ZNC 1.8.1 - https://znc.in]
xwvvvvwx has joined #nixos-dev
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
Jackneill has quit [Ping timeout: 256 seconds]
Jackneill has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
disasm has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
dongcarl has quit [Quit: Ping timeout (120 seconds)]
dongcarl has joined #nixos-dev
<hexa-> Mic92: I'm seeing lots of "Wait for ofborg / tests (pull_request")" fails after 10 minutes
<{^_^}> #94070 (by dmrauh, 1 hour ago, open): pythonPackages.webdavclient3: init at 3.14.5
<Mic92> hexa-: I will try to increase the timeout limit
<Mic92> I wonder why it takes so long for ofborg to start?
<hexa-> idk
<Mic92> Or if it is github
<hexa-> maybe talk to the people in #nixos-borg about what a reasonable timeout is
<Mic92> It does not break anything right now, and it should be clear that this should not block prs.
rajivr has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
<Mic92> hexa-: I think I need to disable somehow in forks too.
<hexa-> Mic92: pretty sure that is a setting in the repo/org
<Mic92> domenkozar[m]: can you check the box for this?
<hexa-> hmm
<hexa-> no, that seems unrelated and only about third-party actions
<Mic92> ah
<Mic92> Ok. Maybe I can check if repository == NixOS
<domenkozar[m]> Mic92: what box? :)
<hexa-> domenkozar[m]: nvm
<Mic92> domenkozar[m]: Nevermind. We want to disable our github action for anything but the main repo
<hexa-> Mic92: there is a workaround in the post
<Mic92> Yes
<Mic92> I will apply that
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
phreedom has quit [Ping timeout: 240 seconds]
phreedom_ has joined #nixos-dev
drakonis has joined #nixos-dev
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
alp has quit [Ping timeout: 240 seconds]
cole-h has joined #nixos-dev
alp has joined #nixos-dev
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
rajivr has quit [Quit: Connection closed for inactivity]
<kalbasit> Ericson2314: Hey there! I'm currently trying to fix an issue building Bazel on Darwin: https://github.com/NixOS/nixpkgs/issues/93787
<{^_^}> #93787 (by kalbasit, 3 days ago, open): Bazel is currently broken on Darwin
<kalbasit> I believe it got broken by the recent changes to the C toolchain
<kalbasit> would you be able to help us out here?
<kalbasit> cc LnL as well
<Ericson2314> kalbasit: i am afraid i am pretty busy ATM
<Ericson2314> looking at the logs I...don't see the original errors?
<Ericson2314> is it possible they are up above due to parallel building?
<kalbasit> Ericson2314: I think the error is this: ld: library not found for -lstdc++
<Ericson2314> kalbasit: there are some new flags files in nix-support/*
<Ericson2314> make sure that bazel gets them too
<Ericson2314> libcxx-cxxflags for example IIRC
<kalbasit> Ericson2314: If I don't touch NIX_LDFLAGS, will they get automatically taken into account?
<kalbasit> NIX_LDFLAGS env var that is
<Ericson2314> with regular builds, yes, but who the hell knows what tricks Bazel is going to pull
<LnL> I don't know much about bazel, but it does it's own messy wrapper stuff IIR
<Ericson2314> I would look at the bazel packaging and build bazel package and see if it is munging flags already
<Ericson2314> and just try to cargo cult that for the new files
<kalbasit> I'll try a few things then. I'll try to remove our custom NIX_*FLAGS first, if that does not work, I'll try to make it source the nix-support files
<kalbasit> If I understand it correctly, those nix-support flag files are the only flags that we need right? As in, I should not try to append to NIX_*FLAGS but instead make it equal that content?
drakonis has quit [Quit: WeeChat 2.8]
<kalbasit> apologies for the noob questions, I'm not the best person when it comes to C toolchain in Nix
<LnL> well it's kind of expected that extending NIX_*CFLAGS in your expressions will be honored
<kalbasit> Right, but I'm wondering if I should be mergeing NIX_*FLAGS with the nix-support files, or just export it with a new value that is the content of the nix-support files
<LnL> ah, don't think that really matters
<kalbasit> got it. I'll get back to you with what I find on this
<LnL> just as long as the compiler is called with everything internally
alp has quit [Ping timeout: 256 seconds]
kini has joined #nixos-dev
justanotheruser has quit [Ping timeout: 246 seconds]
justanotheruser has joined #nixos-dev
drakonis has joined #nixos-dev
jonringer has joined #nixos-dev
<kalbasit> I'm pretty sure it has something to do with the nix-support/libcxx-ldflags which sets -stdlib to libc++. However, it breaks if I add that to NIX_LDFLAGS so I'm not sure where to add that.
<Profpatsch> I like the new stale bot message
<Profpatsch> kalbasit: Ah, if the nix flags changed, that probably clashes with some of the fixes we do on darwin
<Profpatsch> kalbasit: there’s a few darwin-specific blocks in the bazel build expression, you might find something relevant in there?
alp has joined #nixos-dev
theotherjimmy[m] has quit [Ping timeout: 244 seconds]
Guest80879 has quit [Ping timeout: 260 seconds]
puzzlewolf has quit [Ping timeout: 244 seconds]
domenkozar[m] has quit [Ping timeout: 244 seconds]
Valodim[m] has quit [Ping timeout: 244 seconds]
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 260 seconds]
theotherjimmy[m] has joined #nixos-dev
Guest80879 has joined #nixos-dev
Valodim[m] has joined #nixos-dev
Cale has quit [Ping timeout: 260 seconds]
drakonis has joined #nixos-dev
domenkozar[m] has joined #nixos-dev
puzzlewolf has joined #nixos-dev
jonringer_ has joined #nixos-dev
jonringer has quit [Ping timeout: 260 seconds]
Cale has joined #nixos-dev
TethysSvensson has joined #nixos-dev
<TethysSvensson> Hi, I'm new to nixos, so I'm sorry if this is the wrong place to ask. I'm having some trouble finding a reviewer for my first PR (https://github.com/NixOS/nixpkgs/pull/92581). I was wondering if there is something else I should be doing to get feedback on this, or if I should just be patient?
<{^_^}> #92581 (by TethysSvensson, 3 weeks ago, open): busybox: Add a default udhcpc dispatcher script
alp has quit [Ping timeout: 240 seconds]
justanotheruser has quit [Ping timeout: 272 seconds]
<gchristensen> TethysSvensson: thanks for raising it here. I'll leave a few comments on the PR
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
<kalbasit> Profpatsch: yes that's where I'm mostly focusing.
__monty__ has quit [Quit: leaving]
<{^_^}> firing: RootPartitionLowInodes: https://status.nixos.org/prometheus/alerts
drakonis_ has quit [Ping timeout: 240 seconds]
m1cr0man has quit [Quit: G'luck]
m1cr0man has joined #nixos-dev
justanotheruser has joined #nixos-dev
drakonis_ has joined #nixos-dev
TethysSvensson has quit [Remote host closed the connection]
cole-h has quit [Quit: Goodbye]
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 265 seconds]
orivej_ has joined #nixos-dev