!UNVBThoJtlIiVwiDjU:nixos.org

Staging

317 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen109 Servers

Load older messages


SenderMessageTime
30 Aug 2021
@vcunat:matrix.orgVladimír ČunátYes, another possibility is that you've drained the shares and that's why you didn't get much for some time.19:23:01
@vcunat:matrix.orgVladimír ČunátAlso note that stable release jobsets have even much higher amount of shares than haskell.19:24:02
@sternenseemann:systemli.orgsterniI think the high share count for haskell-updates could also stem from the fact that a full rebuild wouldn't be too many jobs in the past (<5000) 19:40:11
@sternenseemann:systemli.orgsternisince we now support more platforms and have more working packages in general, we have a more respectable scheduled job count on a full rebuild which is probably also beneficial for getting builds scheduled19:41:02
31 Aug 2021
@andi:kack.itandi-
In reply to @vcunat:matrix.org
I lowered them now. nixos-unstable is still waiting for the first bump with new openssl.
Anyone able to up the shares again? We've tons of idle x86_64 capacity but due to the 100 shares limit none of the jobs are actually being schedule there... At this rate it'll take way over a week what usually takes ~8hs. There are also 37k jobs in the queue. Not sure why they aren't being picked up. Probably also out of shares on those jobsets?
23:35:54
1 Sep 2021
@hexa:lossy.networkhexa(this is about the systemd-v249 jobset)00:54:08
@vcunat:matrix.orgVladimír Čunát staging-next-21.05 (i.e. the first 21.05 with secure openssl) has over 30k queued x86_64-linux jobs. So I can't see what you mean about the idle capacity. 04:30:59
@vcunat:matrix.orgVladimír ČunátI also thought the shares only affect relative priorities, i.e. if there's free capacity, I expect the matching jobs to get scheduled regardless of shares.04:32:21
@vcunat:matrix.orgVladimír Čunát (OK, the "runnable" metrics are better for judging the scheduling at a particular moment, but even that one's in thousands.) 04:36:47
@andi:kack.itandi-
In reply to @vcunat:matrix.org
staging-next-21.05 (i.e. the first 21.05 with secure openssl) has over 30k queued x86_64-linux jobs. So I can't see what you mean about the idle capacity.
I looked at the machines dashboard of hydra and there were ~4 x86_64-linux machines for about 30min that didn't execute a single job
11:58:17
@vcunat:matrix.orgVladimír Čunát
In reply to @andi:kack.it
I looked at the machines dashboard of hydra and there were ~4 x86_64-linux machines for about 30min that didn't execute a single job
Maybe they're stuck. We certainly have some macs that haven't made a step for days.
11:59:41
@hexa:lossy.networkhexait really seemed like the x86_64-linux machines were idle yesterday, I often saw no x86_64-linux jobs in the running builds12:11:04
@vcunat:matrix.orgVladimír Čunát Weird. I noticed that the /machines page isn't very precise, e.g. it seemed not to show jobs that take relatively short time... for this the /queue-runner-status seemed better. 12:22:57
@hexa:lossy.networkhexathe machine page also shows machines as idle when they're copying stuff12:31:55
@vcunat:matrix.orgVladimír Čunát Well, the scheduling certainly isn't ideal. Now I looked at t4b, and it's been completely idle during the last 15 minutes, not even I/O waits. 12:44:47
@vcunat:matrix.orgVladimír Čunát * Well, the scheduling certainly isn't ideal. Now I looked at t4b, and it's been completely idle during the last 15 minutes, not even I/O waits. (I ran atop on it) 12:45:14
@vcunat:matrix.orgVladimír Čunát The runner status says: "currentJobs" : 4 :-) 12:46:13
@hexa:lossy.networkhexa Vladimír Čunát: hm, what was you reasoning behind merging staging-next-21.05? 20:51:24
@vcunat:matrix.orgVladimír ČunátGetting updated 21.05-small.20:52:14
@vcunat:matrix.orgVladimír Čunát(I tried explaining in the commit message)20:52:30
@vcunat:matrix.orgVladimír ČunátAnd missing binaries on a release branch seem less hurtful than on master.20:53:06
@hexa:lossy.networkhexaGitHub isn't very forthcoming with the merge commit's message20:53:13
@hexa:lossy.networkhexaat least not from within the pull request20:53:38
@hexa:lossy.networkhexaFWIW: I don't mind, was just wondering because there was >50k jobs left20:54:01
@vcunat:matrix.orgVladimír ČunátAh, right... there's a PR :-)20:55:16
@hexa:lossy.networkhexaah, you merged from the CLI? :P20:56:23
@vcunat:matrix.orgVladimír ČunátYes, I typically merge from CLI. (and sign them)20:56:51
@vcunat:matrix.orgVladimír ČunátThe original motivation of -small channels was for faster delivery of security updates. Staging them (partially) defeats that.20:58:12
@vcunat:matrix.orgVladimír ČunátActually, aarch64-linux has no more runnables in queue ATM, if I look right.21:34:02
@vcunat:matrix.orgVladimír ČunátSo this will put it back to work.21:34:08

Show newer messages


Back to Room ListRoom Version: 6