!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

254 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.100 Servers

Load older messages


SenderMessageTime
18 Oct 2024
@raitobezarius:matrix.orgraitobezarius(I try to keep all the deployments proper wrt to git state but I do sometimes push hotfixes without pushing to git, please yell at me if I do that too often)23:19:49
@jade_:matrix.orgjade_yeah, i was scared that there was a loadbearing one of those23:20:01
@jade_:matrix.orgjade_so i had assumed you had a lock on the machine23:20:05
@jade_:matrix.orgjade_if whatever is in main is clean, i can go from there23:20:16
@raitobezarius:matrix.orgraitobezariusI lied ; give me a se23:21:11
@raitobezarius:matrix.orgraitobezarius+c23:21:13
@raitobezarius:matrix.orgraitobezarius it's not a lie anymore: https://git.lix.systems/the-distro/infra/pulls/143 23:23:00
@raitobezarius:matrix.orgraitobezarius.oO(really need to fix that "lock machine" concept once and for all)23:23:28
@raitobezarius:matrix.orgraitobezariusapologies23:23:45
@bb010g:matrix.orgDusk is https://buildbot.lix.systems/#/buildrequests/197977 a transient failure? 23:29:07
@jade_:matrix.orgjade_
In reply to @bb010g:matrix.org
is https://buildbot.lix.systems/#/buildrequests/197977 a transient failure?
that's what usually happens if you push your CL
23:29:37
@jade_:matrix.orgjade_did it happen in another condition?23:29:44
@bb010g:matrix.orgDusk
In reply to @jade_:matrix.org
did it happen in another condition?
i'm not totally sure what you mean by "condition", but i don't believe so. tests reliably pass for me and nothing related changed AFAICT.
23:30:19
@jade_:matrix.orgjade_
In reply to @bb010g:matrix.org
i'm not totally sure what you mean by "condition", but i don't believe so. tests reliably pass for me and nothing related changed AFAICT.
like, this happens if you push a new revision of your CL and the old one gets cancelled
23:30:40
@bb010g:matrix.orgDuskah, i see23:30:46
@jade_:matrix.orgjade_there should be a new CL run for the new revision23:30:55
@bb010g:matrix.orgDuski haven't pushed since about an hour ago, so would that be an old queued run?23:31:26
@jade_:matrix.orgjade_possible23:31:37
@bb010g:matrix.orgDusk ah, https://buildbot.lix.systems/#/builders/1/builds/6144 actually reports it as obsoleted. my bad. 23:32:28
@jade_:matrix.orgjade_yeah. to be clear, we are also aware that the buildbot is incredibly slow :/23:32:52
@raitobezarius:matrix.orgraitobezarius We should probably consider some regular synchronous meeting on Lix infra someday, @jade_:matrix.org: so we can sync on things and I can take care of things synchronously as well 23:35:53
@jade_:matrix.orgjade_yeah23:36:00
@raitobezarius:matrix.orgraitobezarius(e.g. pyroscoping the Buildbot, etc.)23:36:12
@jade_:matrix.orgjade_yeah23:36:18
@raitobezarius:matrix.orgraitobezariusWill send a meet.dgnum.eu later so we can decide on a date and maybe set this as recurring based on the needs23:37:49
@jade_:matrix.orgjade_looking at the profiler code (which i didn't notice was kinda abandoned looking till now), we should just pyroscope it23:47:20
@jade_:matrix.orgjade_there's not a whole lot of reason to need buildbot specific integration for the profiling besides knowing why a particular endpoint is bad23:47:42
@jade_:matrix.orgjade_but our problems are so egregious that we should find plenty enough from overall profiling23:47:58
19 Oct 2024
@jade_:matrix.orgjade_ raitobezarius: reminder on https://gerrit.lix.systems/c/lix/+/1828 00:06:25
@jade_:matrix.orgjade_going to roll a 2.91.1 finally, i think00:34:15

Show newer messages


Back to Room ListRoom Version: 10