!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

476 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.150 Servers

Load older messages


SenderMessageTime
22 Jun 2026
@vcunat:matrix.orgVladimír Čunát Now I'm force-updating the nixos-26.05 channel to e8210c649915 / https://hydra.nixos.org/build/331669102 06:51:28
@arianvp:matrix.orgArianNope we don't do negative caching. That was very much on purpose iirc? 06:55:10
@vcunat:matrix.orgVladimír ČunátIt's certainly not a problem not to cache those, as long as it doesn't cost us much.06:56:59
@vcunat:matrix.orgVladimír Čunát* It's certainly fine not to cache those, as long as it doesn't cost us much.06:57:11
@vcunat:matrix.orgVladimír Čunát

Also this one, it was 7 days old commit

8c14fa3ccacd..ea68a74f45ad  nixpkgs-26.05-darwin
08:25:24
@joerg:thalheim.ioMic92https://github.com/NixOS/infra/pull/1097 with this we got now release-26.05-small back to green: https://hydra.nixos.org/eval/182648609:54:01
@arianvp:matrix.orgArian
In reply to @vcunat:matrix.org
It's certainly fine not to cache those, as long as it doesn't cost us much.

We do get charged for 404s and 200s just the same.

Idk what the ratio between uncached 404s and 200s is. We can look this up in fastly.

Caching 404s definitely saves money. But idk how much.

But we currently don't cache them exactly so that we don't have read after write inconsistencies.

10:01:42
@vcunat:matrix.orgVladimír ČunátI don't think the old queue-runner would mind.10:02:32
@vcunat:matrix.orgVladimír Čunát(it wasn't pulling from Fastly IIRC)10:02:46
@vcunat:matrix.orgVladimír ČunátI don't expect it's a major concern right now anyway.10:03:24
@vcunat:matrix.orgVladimír ČunátMaybe a future TODO to investigate.10:03:29
@hexa:lossy.networkhexaelated-minsky is fairly idle and constantly shows capacity: no11:15:39
@hexa:lossy.networkhexaRedacted or Malformed Event11:15:44
@hexa:lossy.networkhexaRedacted or Malformed Event11:15:54
@hexa:lossy.networkhexa I checked store dir and build dir is available (>20%) and pressure is normal 11:16:28
@hexa:lossy.networkhexathe only remaining check I can't evaluate in my head is11:16:47
@hexa:lossy.networkhexa
        let now = jiff::Timestamp::now().as_second();
        let jobs_in_last_30s_start = self.stats.jobs_in_last_30s_start.load(Ordering::Relaxed);
        let jobs_in_last_30s_count = self.stats.jobs_in_last_30s_count.load(Ordering::Relaxed);

        // ensure that we dont submit more than 4 jobs in 30s
        if now <= (jobs_in_last_30s_start + 30)
            && jobs_in_last_30s_count >= 4
            // ensure that we havent already finished some of them, because then its fine again
            && self.stats.get_current_jobs() >= 4
        {
            return false;
        } else if now > (jobs_in_last_30s_start + 30) {
            // reset count
            self.stats
                .jobs_in_last_30s_start
                .store(0, Ordering::Relaxed);
            self.stats
                .jobs_in_last_30s_count
                .store(0, Ordering::Relaxed);
        }

11:16:51
@hexa:lossy.networkhexaRedacted or Malformed Event11:16:53
@hexa:lossy.networkhexaRedacted or Malformed Event11:16:57
@hexa:lossy.networkhexahm, ok. now it's back to building packages and it runs more jobs, previously it was busy with nixos tests11:18:12
@hexa:lossy.networkhexaalso the queue has a new eval11:18:42
@hexa:lossy.networkhexayeah, I think we're running into that 4 jobs limit a lot11:44:25
@joerg:thalheim.ioMic92Maybe but we also regressed in performance when I had to go back to using the nix-daemon for more stuff. I try to get some of the performance back but as long as things are somewhat stable now, I would like to move a bit slower and do more testing11:48:39
@vcunat:matrix.orgVladimír ČunátDid buildMozillaMach already suffer from silent-timeouts during the final link?12:21:02
@hexa:lossy.networkhexayou mean before today? I'd say no12:21:22
@vcunat:matrix.orgVladimír Čunáte.g. this 3h build got it twice already: https://hydra.nixos.org/build/331659622#tabs-buildsteps12:21:36
@hexa:lossy.networkhexasilent-timeout on linux should be 3h12:22:06
@hexa:lossy.networkhexaso let me just say that 2h 59m 2s is under 3h12:22:23
@vcunat:matrix.orgVladimír ČunátMaybe we're not applying it correctly with the new queue-runner anymore? 🤔12:22:37
@vcunat:matrix.orgVladimír Čunát* Maybe we're not applying such settings correctly with the new queue-runner anymore? 🤔12:23:01

Show newer messages


Back to Room ListRoom Version: 6