gchristensen changed the topic of #nixos-borg to: https://www.patreon.com/ofborg https://monitoring.nix.ci/dashboard/db/ofborg?refresh=10s&orgId=1&from=now-1h&to=now "I get to skip reviewing the PHP code and just wait until it is rewritten in something sane, like POSIX shell. || https://logs.nix.samueldr.com/nixos-borg
<{^_^}> [ofborg] @tilpner opened pull request #281 → Add tilpner to extra-known-users → https://git.io/fpo3T
<{^_^}> [ofborg] @grahamc pushed 2 commits to checks-api: https://git.io/fponz
<{^_^}> [ofborg] @grahamc opened pull request #282 → Checks → https://git.io/fponM
<{^_^}> [ofborg] @grahamc pushed 2 commits to checks-api: https://git.io/fpoC8
<{^_^}> [ofborg] @grahamc pushed to checks-api « things segfault lol »: https://git.io/fpoWT
<samueldr> !
<gchristensen> ?
<samueldr> that commit message
<gchristensen> oh
<gchristensen> yeah
<gchristensen> its probably something crappy about travis
<gchristensen> but I dunno
<gchristensen> Updating git repository `https://github.com/grahamc/rust-amqp.git`
<gchristensen> /nix/store/kc8llivfvmm819nh2brfn7n4ppl2djg8-stdenv-linux/setup: line 99: 13408 Segmentation fault (core dumped) cargo test --lib
<gchristensen> also lol nix1 doesn't compile on master anymore?
<{^_^}> [ofborg] @grahamc pushed to checks-api « Try random stuff to make tests run in Travis »: https://git.io/fpoWu
<gchristensen> ok lol well since I can't get travis to work, I guess my laptop is going in to production for the night
<{^_^}> [ofborg] @grahamc pushed to checks-api « cargo test without --lib »: https://git.io/fpoWp
<{^_^}> [ofborg] @grahamc pushed to checks-api « cargo test without --lib (for real) »: https://git.io/fpolq
orivej has joined #nixos-borg
tilpner has joined #nixos-borg
<tilpner> Hey gchristensen, seeing as how you use the minio PR for the checks announcement, here's some questions disguised as feedback
<tilpner> Actually... no questions. Do you control the labels of the tabs on the checks tab?
<tilpner> The label says "nix build -A minio -A minio-cli..." for each of them here
<tilpner> While it should mention the aarch64-linux, because that's the only information that differs across tabs
<tilpner> So maybe just pull that argument to the start of the invocation and hope it fits :/
<tilpner> And what do you make of this log? Is it really the full log? https://github.com/NixOS/nixpkgs/pull/51300/checks?check_run_id=36684399
<tilpner> It would mean someone pushed the exact version I'm PR-ing to the cache?
<tilpner> Oh, and I like that it uses the checks API instead of comments now
<tilpner> I looked for a way to ignore notifications from specific users (=ofborg) a few times
<tilpner> And are you certain about building multiple package in one nix-build? I think it would more readable sequentially
<tilpner> Oh, and did you ask the foundation for some money?
<tilpner> I don't know how much money they have, but I'd rather increase my donation to them instead of donating to different parts of NixOS infrastructure individually
orivej has quit [Ping timeout: 268 seconds]
<LnL> the build probably ended up on the same machine again
<tilpner> LnL - But it was supposed to have never been built before?
<LnL> that's the first build
<tilpner> But why were there two builds at all?
<tilpner> Is that because the PR has two commits?
<LnL> maybe it was triggered twice
<tilpner> There is only @ofborg build ... comment
<LnL> yeah but it was probably restarted, don't worry about it
<tilpner> Well, I don't mind this particular instance
<tilpner> But it did confuse me, so it'd be important to know if it happens more often
<LnL> I've thought about it before, nix keeps the build log around so we could replay it
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 250 seconds]
<gchristensen> tilpner: do I control the labels? yes https://github.com/NixOS/ofborg/blob/c77e5231e3e43dccc9f1b8a8e335f721008f73fb/ofborg/src/tasks/githubcommentposter.rs#L136 - please leave feedback about the checks experience here: https://github.com/NixOS/ofborg/pull/282
<{^_^}> ofborg#282 (by grahamc, 10 hours ago, open): Checks
<gchristensen> And are you certain about building multiple package in one nix-build? I'm certain that is what it does now :)
<gchristensen> Oh, and did you ask the foundation for some money? no, I try to leave that money for hydra and whatnot
<gchristensen> I bet I know why the thing built twice ... the new App created a new Webhook and maybe I stupidly put in the identical key
<gchristensen> I changed the dupe's key, so those should be discarded dnow
<tilpner> gchristensen - Yes, I realise it currently builds two at once. I'm proposing it doesn't
<gchristensen> yes
<gchristensen> all I'm certain about is what it does now
<tilpner> Are you saying it currently builds sequentially?
<gchristensen> no, it builds them all at once
<gchristensen> you're right about its behavior
<tilpner> Do you agree it may be confusing that output is interleaved?
<gchristensen> yes
<tilpner> Good, I'll comment that too on the issue
<gchristensen> that should probably be a new issue
<tilpner> :/
<gchristensen> ofborg has always built them together like that, it isn't changing w/ checks
<gchristensen> I'm not intentionally being a butt. I meant to take the stance of: I'm not attached to it building everything at once in the same output stream. indeed, with Checks, it becomes feasible to build them separately. however, that does make the builders more complicated (unless they're sequential builds... which would make it slower)
<tilpner> Oh, do they update live too?
<tilpner> You can still build both in parallel, save the output, then hand them to checks sequentially
<gchristensen> no, because the builders do live-streaming of logs
<tilpner> That is not entirely incompatible with live updates, it just makes them annoying to read
<tilpner> You would have to retransmit the entire thing every time though :/
<gchristensen> yeah, not gonna do that
<tilpner> Maybe have interleaved live updates while it's building, but also tee output to individual files and reorder them for the final check result?
<gchristensen> I'd rather list the drv's needed to build and have a thread pool of nix builders building DRVs to stream back
<gchristensen> no, it is annoying to update builders, since I don't control them all. I don't want to get fancy without doing the fanciness very robustly.
<tilpner> Oh, okay
<LnL> yeah, separating evaluation and builds would be nice
<LnL> but then that needs to be distributed somehow
<gchristensen> so either of y'all seen Cargo segfault on Travis?
<gchristensen> b/c my laptop can't stay in prod for very long, it has poor uptime qualities
<LnL> I tried earlier and I can reproduce
<gchristensen> I've thought about trying different channels, but it takes so long to get Carnix to work I gave up for the night. I'll give that a go here after a dog walk
<gchristensen> LnL: oh, I dropped some isDarwin stuff. does it still compile properly with nix-build for you?
<gchristensen> hmmm maybe a cargo build followed by cargo test
<LnL> it's the build part
<{^_^}> [ofborg] @grahamc pushed to checks-api « cargo build then test »: https://git.io/fpoV2
<gchristensen> I guess my hope is that it'll approach it differently and not die :/
<LnL> for what I can tell cargo uses libgit and something in there dies
<LnL> something something, network access during a build is evil, something something
<gchristensen> :D
<gchristensen> I very much wish the nix build would run `cargo test` or whatever. it would make this a non-issue
<LnL> yeah, I know nothing about carnix but presumably it's possible to make cargo use those dependencies instead
<gchristensen> I try not to look too deeply at carnix right now -- it changes enough between when I use it :)
<LnL> have you tried to run cargo clean and/or remove ~/.cargo on your machine?
<gchristensen> hmm not yet :)
<gchristensen> I will try after I get some coffee brewing
<gchristensen> LnL: wait, so, you can't `cargo build` on your machine at ll?
<gchristensen> I misunderstood what you meant by reproduce :)
<LnL> not on the checks branch
<LnL> both darwin and linux btw
<gchristensen> impressive
<LnL> segfaults for everybody!
<gchristensen> equal opportunity segfaulter, apparently
<gchristensen> except for me
<LnL> I suspect the gist stuff is cached from a build with a different cargo on you machine
<LnL> git*
<gchristensen> yes, I think you're right
<gchristensen> [nix-shell:~/projects/ofborg/ofborg]$ cargo build
<gchristensen> Updating git repository `https://github.com/grahamc/rust-amqp.git`
<gchristensen> Segmentation fault
<gchristensen> okkkk I'll fire up gdb :)
<gchristensen> "/nix/store/vpi07f89n0hg53sp3d12p3z6zdw9zpc8-cargo-1.30.0/bin/cargo": not in executable format: File format not recognized
<gchristensen> or not
<{^_^}> [ofborg] @grahamc pushed to checks-api « Change to nixos-unstable »: https://git.io/fpowp
<gchristensen> LnL: try nw?
<gchristensen> LnL: want to take a look at my PR?
<gchristensen> looks like I got a fix in.
<LnL> great!
<LnL> I'm kind of afk, how is it possible not to find a dumb notebook after searching for an hour
<gchristensen> uhhh, haha
<gchristensen> segfault is back
<gchristensen> oops
<gchristensen> i lied
<{^_^}> [ofborg] @grahamc pushed 3 commits to checks-api: https://git.io/fpoKz
orivej has joined #nixos-borg
<LnL> do you know what the actual problem is?
<LnL> I feel like something with cargo or git is just broken
<gchristensen> I think libgit2 0.26.6 -> 0.26.8 which fixed some sec vulns broke it
<gchristensen> LnL: can you verify nix-build . -A ofborg.rs works on darwin for https://github.com/NixOS/ofborg/pull/282 ?
<{^_^}> ofborg#282 (by grahamc, 13 hours ago, open): Checks
<{^_^}> [ofborg] @grahamc merged pull request #282 → Checks → https://git.io/fponM
<{^_^}> [ofborg] @grahamc pushed 21 commits to released: https://git.io/fpo6l
<{^_^}> [ofborg] @grahamc pushed 0 commits to checks-api: https://git.io/fpo68
<LnL> it's copying way too much around somehweree
<gchristensen> do you have a target/ dir?
<LnL> no
<LnL> oh look it started building
<gchristensen> woohoo the checks poster isn't running on grahams-laptop-prod anymore
<LnL> hmm 'x86_64-linux' is required to build '...-rust_antidote-1.0.0.drv', but I am a 'x86_64-darwin'
<gchristensen> ...huh
<LnL> I'd have to test a regular build but I'm on edge right now
<gchristensen> I need to step away from the computer for abit
<gchristensen> w00t nix-build is forever enshrined in the Hubcaps client now.
<ekleog> \o/
<gchristensen> #![deny(missing_docs)] -- nice
orivej has quit [Ping timeout: 246 seconds]
<gchristensen> the hilarious thing is that isn't even a doc comment :')
<ekleog> oh nice, didn't notice :'D
orivej has joined #nixos-borg
<gchristensen> yay hacking on libgit2
orivej has quit [Ping timeout: 246 seconds]
<LnL> oh jeeze, you're still on that?
<gchristensen> LnL: some people had some useful tips, so I tried 0.26.7 and it worked ... then someone pointed to a specific commit, and I reverted it, and it works
<{^_^}> rust-lang/cargo#6365 (by grahamc, 2 hours ago, open): Cargo 1.30.0 segfaults with libgit2 0.26.8
<LnL> noce job hunting that down
<gchristensen> mostly @jonas-schievink's work :) I just plugged it in to Nix
<LnL> I wonder why nobody ran into this yet, are we the only distro that updates git? ;)
orivej has joined #nixos-borg
<gchristensen> :)
<gchristensen> ,loot
<{^_^}> [2018-05-26 20:24:58] <gchristensen> 25 points gets you a sticker, 100 points gets you a t-shirt, 1000 verified points gets you a free trip to nixcon *restrictions apply, must be verifiable points, given by grateful people, in channels I'm in