AlwaysLivid has quit [Remote host closed the connection]
AlwaysLivid has joined #nixos-dev
<__monty__>
Where can I find which hardware revision the Hydra Mac Minis are and whether updating the macOS version on them is easy/tedious?
aminechikhaoui8 has joined #nixos-dev
janneke_ has joined #nixos-dev
kraem1 has joined #nixos-dev
orivej_ has joined #nixos-dev
janneke_ is now known as janneke`
Willi_Butz_ has joined #nixos-dev
m1cr0m4n has joined #nixos-dev
ivan_ has joined #nixos-dev
kraem has quit [Ping timeout: 256 seconds]
aminechikhaoui has quit [Ping timeout: 256 seconds]
orivej has quit [Ping timeout: 256 seconds]
janneke has quit [Ping timeout: 256 seconds]
Willi_Butz has quit [Ping timeout: 256 seconds]
m1cr0man has quit [Ping timeout: 256 seconds]
hyperfekt has quit [Ping timeout: 256 seconds]
ivan has quit [Ping timeout: 256 seconds]
kaptin has quit [Ping timeout: 256 seconds]
aminechikhaoui8 is now known as aminechikhaoui
hyperfekt_ has joined #nixos-dev
hyperfekt_ has quit [Max SendQ exceeded]
hyperfekt has joined #nixos-dev
kaptin has joined #nixos-dev
janneke` is now known as janneke
<domenkozar[m]>
__monty__: gchristensen would know more
<gchristensen>
__monty__, domenkozar[m]: this issue has some information about most of the macs: https://github.com/NixOS/nixos-foundation/issues/5 it is somewhat out of date as we've gotten some more hardware recently
<{^_^}>
nixos-foundation#5 (by grahamc, 1 year ago, closed): Spending Request: Upgrades to the the macOS builders
rj has joined #nixos-dev
<__monty__>
gchristensen: Thanks. The Apple Silicon thread has the info on the M1 Minis : )
AlwaysLivid has quit [Remote host closed the connection]
AlwaysLivid has joined #nixos-dev
JonasChevalier[m is now known as zimbatm[m]
AlwaysLivid has quit [Remote host closed the connection]
orivej_ has quit [Ping timeout: 264 seconds]
AlwaysLivid has joined #nixos-dev
orivej has joined #nixos-dev
__monty__ has quit [Quit: leaving]
NinjaTrappeur has quit [Ping timeout: 272 seconds]
NinjaTrappeur has joined #nixos-dev
jonringer has joined #nixos-dev
jonringer has quit [Remote host closed the connection]
<ajs124>
I put my theory in a comment there, but I don't have any machines outside Germany right now, to check if geoip and different mirrors might be the reason.
<gchristensen>
my non-german IP got a matching hash
<ajs124>
hm. so how do we proceed then?
<ajs124>
blame cosmic rays?
<gchristensen>
supersandro2000: can you upload the result you got with that different hash?
<gchristensen>
I just tried fetching from each mirror and despite 3 being down they all returned the same hash
<ajs124>
so... cosmic rays it is?
<gchristensen>
well...
<gchristensen>
if we can get the archive supersandro2000 got ... I'd like to compare ...
<abathur>
domenkozar[m]: I've rebased nix#4289 and nix#4532 on this and commented on each thread with a link to a clean macOS test run :)
<rmcgibbo[m]>
is there any api with hydra to check if a given store path has a cached failure for it? (i know i can use hydra-check to search by attr name).
<gchristensen>
there probably could be
rj has quit [Ping timeout: 268 seconds]
<rmcgibbo[m]>
not _that_ useful, but i noticed that my bot was spending some time rebuilding `mono` on aarch64 in response to some small package bumps, and i can see mono's broken on master for those exact store paths. i'm not sure if anyone else would find a use for such a feature, since they usually want to search by name or attr name, so it might not be worth it.
<gchristensen>
so right now the search is not useful for store paths because the query uses %?% and it takes forever, but an exact match on store paths would be fairly fast
rj has joined #nixos-dev
<rmcgibbo[m]>
i'm sure there are more important features w/ higher priority, but if that existed i'd use it.