!UNVBThoJtlIiVwiDjU:nixos.org

Staging

280 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.05 | Review Reports: https://malob.github.io/nix-review-tools-reports/97 Servers

Load older messages


SenderMessageTime
1 Sep 2021
@vcunat:matrix.orgVladimír Čunát * So this will put it back to work. (ah, probably not too much, just some NixOS tests will get added)21:38:43
3 Sep 2021
@vcunat:matrix.orgVladimír Čunát
In reply to @andi:kack.it
I'm currently testing the PR rebased on master (with a hydra jobset) so ideally the amount of (additional) rebuilds will be very small anyway.

I don't expect the systemd jobset really helps to reduce the rebuilds much. It's small - only has about one thousand builds, but OfBorg says the full rebuild amount is >26k.

Also, I assume you didn't mean for systemd to go before the staging-next iteration that's been in progress for more than a week (?), and their combination will cause rebuilds again.

05:59:17
@andi:kack.itandi-It isn't about rebuilds but getting the testes executed. Also to be able to verify on local devices without days of rebuilding things locally. I don't expect it to merge apart from any of the usual staging flows.06:00:43
@andi:kack.itandi-* It isn't about rebuilds but getting the testes executed. Also to be able to verify on local devices without days of rebuilding things locally. I don't expect it to be merged outside of any of the usual staging flows.06:02:56
@vcunat:matrix.orgVladimír ČunátAh, so it just waits if there's more feedback and then will get merged to staging? Even staging-next would seem OK at this moment, given that you've tested it relatively a lot and it staging-next doesn't have that many binaries ATM (and x86_64-darwin is lagging way behind and won't suffer from systemd).06:04:48
@vcunat:matrix.orgVladimír Čunát * Ah, so it just waits if there's more feedback and then will get merged to staging? Even staging-next would seem OK at this moment, given that you've tested it relatively a lot and staging-next doesn't have that many binaries ATM (and x86_64-darwin is lagging way behind and won't suffer from systemd).06:05:18
@andi:kack.itandi-Yeah, I don't think it is very risky right now. There is one minor change pending and then it is good to go. I'll have a look at that in the evening. By then all the pending tests are hopefully through.06:07:21
4 Sep 2021
@andi:kack.itandi-FWIW I think the PR is "final". I've gone through most of the hydra build failures and I couldn't find anything that would come from my changes. Retargeted the PR to staging-next so we can merge it in whenever you want.16:33:46
5 Sep 2021
@hexa:lossy.networkhexa
Your branch is ahead of 'origin/staging-next' by 485 commits.
12:52:07
@lukegb:zxcvbnm.ninjalukegb (he/him) joined the room.12:52:29
@hexa:lossy.networkhexamerged12:53:44
@hexa:lossy.networkhexaping me when python issues come up12:54:25
@lukegb:zxcvbnm.ninjalukegb (he/him)ack12:54:34
@lukegb:zxcvbnm.ninjalukegb (he/him)hmm, imagemagick bump in there too?12:54:40
@hexa:lossy.networkhexaah fuck12:55:10
@hexa:lossy.networkhexaI forgot to rebase12:55:15
@hexa:lossy.networkhexabrb12:55:17
@hexa:lossy.networkhexa * ah fck12:57:10
@hexa:lossy.networkhexareverted, rebased, merged, pushed.13:03:16
@hexa:lossy.networkhexasorry :)13:03:18
@lukegb:zxcvbnm.ninjalukegb (he/him)no worries :) thanks for the quick fix13:03:27
@hexa:lossy.networkhexaplease double-check13:03:46
@hexa:lossy.networkhexabut it lgtm13:04:18
@lukegb:zxcvbnm.ninjalukegb (he/him)hmm13:05:38
@lukegb:zxcvbnm.ninjalukegb (he/him)we're missing charset-normalizer13:05:42
@hexa:lossy.networkhexathat broke stuff.13:05:44
@hexa:lossy.networkhexapicking it13:06:20
@hexa:lossy.networkhexaso much confidence lost 🤐13:06:53
@lukegb:zxcvbnm.ninjalukegb (he/him)yeah, trying to pull together a mishmash of staging and python-unstable is going to be pain13:08:44
@hexa:lossy.networkhexaindeed13:09:02

There are no newer messages yet.


Back to Room ListRoom Version: 6