<ekleog> https://github.com/NixOS/nixpkgs/pull/34971#issuecomment-374068840 don't get it, didn't the patch fail to apply before?
<gchristensen> huh?
<ekleog> or is ofborg non-deterministic?
<ekleog> oh, maybe it just ran twice and one gcc build passed and not the other, nvm
<gchristensen> yes probably
<gchristensen> the first one probably ran on a faster CPU than the second one
<{^_^}> [ofborg] @grahamc merged pull request #136 → Pass a request-id along with build jobs and results → https://git.io/vx3M3
<{^_^}> [ofborg] @grahamc pushed 2 commits to next: https://git.io/vx3DS
<{^_^}> → e86fc6b7 by @grahamc: Pass a request-id along with build jobs and results
<{^_^}> [ofborg] @grahamc pushed 0 commits to request-id: https://git.io/vx3D9
<{^_^}> → 022e2090 by @grahamc: Merge pull request #136 from NixOS/request-id
<gchristensen> samueldr: ^ that is a funny message :) I deleted the branch
<samueldr> tell that to git and github :) though that's a trivial one to remove
<samueldr> (issue created)
<gchristensen> :)
<gchristensen> ps there is a fun new toy for you to play with in the logs
<gchristensen> "request_id":null <- will soon always be filled, to group all the results by request
<samueldr> have you thought about adding a timestamp so the tabs can be ordered, and so it can be shown?
<gchristensen> I've sort of been avoiding time
<gchristensen> heh
<samueldr> only the moment it's queued, as a replacement for absolute ordering, or alternatively, absolute ordering
<samueldr> GUIDs make it hard to navigate
<gchristensen> agreed
<samueldr> though, grouping will help
<gchristensen> I think we're getting close to where the UI can be rich without time
<gchristensen> and hide the guids
<gchristensen> being able to group the replies together and knowing what is being built by each one now
<{^_^}> [ofborg] @grahamc pushed to next « Own the merge conflict label »: https://git.io/vx3HD
orivej has quit [Ping timeout: 264 seconds]
MichaelRaskin has quit [Quit: MichaelRaskin]
orivej has joined #nixos-borg
jtojnar has quit [Remote host closed the connection]
nicoopa has joined #nixos-borg
nicoopa has quit [Client Quit]
orivej has quit [Ping timeout: 260 seconds]
jtojnar has joined #nixos-borg
jtojnar_ has joined #nixos-borg
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-borg
jtojnar_ has quit [Ping timeout: 264 seconds]
MichaelRaskin has joined #nixos-borg
jtojnar_ has joined #nixos-borg
jtojnar has quit [Ping timeout: 240 seconds]
jtojnar_ is now known as jtojnar
<MichaelRaskin> Now that I played with utilisation rate for ofborg, I wonder how many pieces of hardware are behind the builder instance numbers…
<gchristensen> :)
<MichaelRaskin> An interesting state of the builder box: connection to port 22 can be established, by SSH banner never comes.
<gchristensen> huh?
<MichaelRaskin> (I had to reboot it, obviously)
<gchristensen> oh
<MichaelRaskin> I don't know what has happenned to it exactly, but I wonder whether this makes a mess when it happens during a build…
<MichaelRaskin> I cannot exclude that the problem was HDD controller deciding to take too long to reply to something, with system getting disappointed and losing faith in the filesystem, or something like that.
<MichaelRaskin> Given I am prepared to lose all the HDD contents on this box, I have no incentive to care as long as replugging the HDD once a month somehow keeps the box booting…
<MichaelRaskin> (same HDD, same cable, the only slot)
<gchristensen> :o :D
<MichaelRaskin> I don't know exactly what's wrong. I know cheap HDDs nowadays like to go crazy with age.
<MichaelRaskin> It is a Brix — a small, and therefore slightly overheated, machine
<gchristensen> aahhh yes
<MichaelRaskin> But backpackable if needed!
<gchristensen> I had a Brix
<MichaelRaskin> This is an i7-4770R Brix. So it does overheat.
<gchristensen> whoa no kidding
jtojnar_ has joined #nixos-borg
jtojnar has quit [Ping timeout: 240 seconds]
jtojnar_ is now known as jtojnar
orivej has joined #nixos-borg
gchristensen has quit [Quit: WeeChat 1.9.1]
gchristensen has joined #nixos-borg
<cransom> the tiny little intel nuc machines have been good to me. never had any stability problems on my little i5-3somethings.
<gchristensen> be me after a long day
<gchristensen> spend 15 minutes trying to figure out what is going on with: curl: (1) Protocol "htts" not supported or disabled in libcurl
<cransom> i have no idea what you are talking about. i've never done that *looks around nervously*
<gchristensen> lol
jtojnar has quit [Read error: Connection reset by peer]
orivej has quit [Ping timeout: 264 seconds]
<dtz> xD