!aGqRytqbCECitOFhbt:nixos.org

Release Management

345 Members
25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html94 Servers

Load older messages


SenderMessageTime
23 May 2024
@arianvp:matrix.orgArian24.05 boots successfully on Amazon 🥳 https://github.com/NixOS/amis/actions/runs/9203089651/job/25314015902?pr=13206:22:53
@arianvp:matrix.orgArianRedacted or Malformed Event06:23:48
@vcunat:matrix.orgVladimír Čunát
In reply to @arianvp:matrix.org
in what way would make it the channel update slower? amazonImage is already part of the tested job
The update process needs to download the image from cache and upload it to the bucket.
06:25:45
@vcunat:matrix.orgVladimír Čunát
In reply to @arianvp:matrix.org
in what way would make it the channel update slower? amazonImage is already part of the tested job
* The update process needs to download the image from S3 and upload it to the bucket.
06:26:07
@arianvp:matrix.orgArianGotcha. So we just move the slowness to somewhere else. Okay. I'll just keep it like this for now06:26:08
@vcunat:matrix.orgVladimír Čunát * The update process needs to download the image from S3 and upload it to the other bucket. 06:26:14
@vcunat:matrix.orgVladimír Čunát

For illustration, let me paste a bit of timestamped log from channel activation (these aren't visible publicly):

May 22 22:13:48 pluto update-nixos-unstable-start[50857]: downloading /nix/store/in1gg39qhphlxj9ryd4k2mqdr7dy5j9j-nixos-plasma6-24.05pre629726.5710852ba686-aarch64-linux.iso/iso/nixos-plasma6-24.05pre629726.5710852ba686-aarc>
May 22 22:13:48 pluto update-nixos-unstable-start[50857]:  $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/in1gg39qhphlxj9ryd4k2mqdr7dy5j9j-nixos-plasma6-24.05pre629726.5710852ba686->
May 22 22:16:35 pluto update-nixos-unstable-start[50857]: downloading /nix/store/qawl76aqcm61vgms1vf8kfm0l21ay6lq-nixos-plasma6-24.05pre629726.5710852ba686-x86_64-linux.iso/iso/nixos-plasma6-24.05pre629726.5710852ba686-x86_6>
May 22 22:16:35 pluto update-nixos-unstable-start[50857]:  $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/qawl76aqcm61vgms1vf8kfm0l21ay6lq-nixos-plasma6-24.05pre629726.5710852ba686->
May 22 22:19:46 pluto update-nixos-unstable-start[50857]: downloading /nix/store/4n8bm9qqllfsi35gmbzxwjsf0f7di405-nixos-gnome-24.05pre629726.5710852ba686-aarch64-linux.iso/iso/nixos-gnome-24.05pre629726.5710852ba686-aarch64->
May 22 22:19:46 pluto update-nixos-unstable-start[50857]:  $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/4n8bm9qqllfsi35gmbzxwjsf0f7di405-nixos-gnome-24.05pre629726.5710852ba686-aa>
May 22 22:22:03 pluto update-nixos-unstable-start[50857]: downloading /nix/store/5kff34rypj8nkhcaan2bpvscmmxfw9j9-nixos-gnome-24.05pre629726.5710852ba686-x86_64-linux.iso/iso/nixos-gnome-24.05pre629726.5710852ba686-x86_64-li>
May 22 22:22:03 pluto update-nixos-unstable-start[50857]:  $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/5kff34rypj8nkhcaan2bpvscmmxfw9j9-nixos-gnome-24.05pre629726.5710852ba686-x8>
May 22 22:24:38 pluto update-nixos-unstable-start[50857]: downloading /nix/store/0zfg4fw0y7wwd5sz6yi3m93zc3h1mxsg-nixos-ova-24.05pre629726.5710852ba686-x86_64-linux/nixos-24.05pre629726.5710852ba686-x86_64-linux.ova to /home>
May 22 22:24:38 pluto update-nixos-unstable-start[50857]:  $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/0zfg4fw0y7wwd5sz6yi3m93zc3h1mxsg-nixos-ova-24.05pre629726.5710852ba686-x86_>
06:29:02
@vcunat:matrix.orgVladimír ČunátAll the three 24.05 channels are there.14:37:52
@vcunat:matrix.orgVladimír ČunátSo I guess this will come soon: https://nixos.github.io/release-wiki/Branch-Off.html#once-the-channel-is-available14:38:25
@vcunat:matrix.orgVladimír ČunátOh, looking at it, only the step (1) is missing, I think.14:40:20
@pederbs:pvv.ntnu.nopbsdsit seems the release schedule does not detail when breaking changes are unrestricted on master. Should than be after branch-off, or after tagging the release?21:12:45
@pederbs:pvv.ntnu.nopbsds * it seems the release schedule does not detail when breaking changes are unrestricted on master. Should this be after branch-off, or after tagging the release?21:13:02
@raitobezarius:matrix.orgraitobezariusjust after branch-off21:13:46
@raitobezarius:matrix.orgraitobezariustagging the release happens on a parallel branch21:13:51
@pederbs:pvv.ntnu.nopbsdsbut this the week of backports. maintaining similarity between master and release-24.05 may be considered benefitial21:14:54
@pederbs:pvv.ntnu.nopbsdsi commonly see comitters skip waiting for ofborg builds on backport during this week21:16:25
@pederbs:pvv.ntnu.nopbsds * i commonly see committers skip waiting for ofborg builds on backport during this week21:16:32
@pederbs:pvv.ntnu.nopbsds * i commonly see committers skip waiting for ofborg builds on backports during this week21:16:41
@raitobezarius:matrix.orgraitobezarius
In reply to @pederbs:pvv.ntnu.no
i commonly see committers skip waiting for ofborg builds on backports during this week
??????????
21:18:25
@lily:lily.flowersLily Foster
In reply to @pederbs:pvv.ntnu.no
but this the week of backports. maintaining similarity between master and release-24.05 may be considered benefitial
similarity yeah. RMs can better say/change when breaking changes are unrestricted. it should probably be clarified in release wiki though (and posted schedules)
21:18:26
@raitobezarius:matrix.orgraitobezariusskipping ofborg builds is not acceptable under any circumstance21:18:38
@lily:lily.flowersLily Foster
In reply to @pederbs:pvv.ntnu.no
i commonly see comitters skip waiting for ofborg builds on backport during this week
(this is a huge problem that needs to be addressed then)
21:18:39
@raitobezarius:matrix.orgraitobezariusa backport is already a quite involved action21:18:46
@raitobezarius:matrix.orgraitobezariusskipping their CI is really unacceptable without a proper provided rationale before the merge or something21:19:02
@lily:lily.flowersLily Foster
In reply to @raitobezarius:matrix.org
skipping ofborg builds is not acceptable under any circumstance
(well skipping eval checks at least. builds can be separately verified)
21:19:09
@lily:lily.flowersLily Foster(which i wouldn't clarify except that the aarch64-darwin build queue exists......)21:19:31
@raitobezarius:matrix.orgraitobezarius
In reply to @pederbs:pvv.ntnu.no
but this the week of backports. maintaining similarity between master and release-24.05 may be considered benefitial
i don't understand why this is the week of backports
21:19:44
@raitobezarius:matrix.orgraitobezariusthis is a bugfixing sequence at most21:19:50
@raitobezarius:matrix.orgraitobezariusnot a "oops i missed the train, let me add my shit" sequence21:19:59
@lily:lily.flowersLily Foster(yeah backports do continue for next 7 months too)21:20:05

Show newer messages


Back to Room ListRoom Version: 6