!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
2 Oct 2025
@guipsp:matrix.orgGuilherme Espada joined the room.18:19:30
3 Oct 2025
@oli:floof.company-> @oli:catgirl.cloud changed their display name from olivia floof company edition [she/it] 🏳️‍⚧️ to -> @oli:catgirl.cloud.09:33:58
@wtvb:matrix.orgulucs changed their display name from wtvb to ulucs.15:05:21
@delroth:delroth.netdelrothlinked to the recent gerrit outage / mild data loss: we're going to migrate gerrit.lix.systems to a new host on Tuesday 2025-10-07. Maintenance window is currently from 17:00 to 20:00 CEST, expect downtime during this period (hopefully we won't need the whole 3h). The host will also be relocated from the US to Western Europe. IP addresses will change but I expect to be able to keep the SSH key, so this should be fairly transparent. We'll re-announce a bit before the maintenance window, at the beginning of the maintenance window, and when the migration ends.21:56:04
5 Oct 2025
@piegames:flausch.socialpiegameshttps://buildkite.com/lix-project/lix/builds/4982/steps/canvas?jid=0199b4f9-45b7-4be9-bf12-d510cc946935 pipeline job running for 3.5h, dis normal?18:52:00
@piegames:flausch.socialpiegamesGrr, Darwin CI seems to be down again18:53:10
@raitobezarius:matrix.orgraitobezariusI don't think it's down18:55:20
@raitobezarius:matrix.orgraitobezariusWe have been just hammering it18:55:23
@raitobezarius:matrix.orgraitobezariusimage.png
Download image.png
18:56:02
@raitobezarius:matrix.orgraitobezariusWe just don't have enough Darwin capacity on our peaks contribution periods18:56:18
@raitobezarius:matrix.orgraitobezariusI'm planning to connect something like 4 more jobs or slightly more18:56:26
@raitobezarius:matrix.orgraitobezariusBut it won't give us 3.5hr/3 peaks18:56:47
@raitobezarius:matrix.orgraitobezariusIf we had a way to make certain Darwin tests which are extremely slow faster, we could cut18:57:02
@piegames:flausch.socialpiegamescan we make Darwin tests non-blocking for merge maybe? :)19:34:52
@piegames:flausch.socialpiegameshow many Darwin-specific tests do we have?19:35:24
@raitobezarius:matrix.orgraitobezariusunit tests mostly?19:36:16
@raitobezarius:matrix.orgraitobezariuswe don't have any integration tests for darwin19:36:27
@raitobezarius:matrix.orgraitobezariusnot a big fan of not making them blocker for merge19:36:38
@raitobezarius:matrix.orgraitobezariusbut happy to drop for example nej19:36:44
@raitobezarius:matrix.orgraitobezarius* but happy to drop for example nej tests19:36:46
@raitobezarius:matrix.orgraitobezariuswhich are notoriously slow19:36:49
@piegames:flausch.socialpiegamesI think we should primarily be smarter about our scheduling19:40:20
@piegames:flausch.socialpiegamesstuff like making round-robin across chains, build first and last commit first, skip all in-between on failure of both19:41:19
@raitobezarius:matrix.orgraitobezariusbesadii can be extended to support this scheduling19:53:30
@raitobezarius:matrix.orgraitobezariusit contains hooks for result reporting and starting up builds19:53:54
@raitobezarius:matrix.orgraitobezariusso it can delay to wait for a chain upload rather than firing up CI jobs immediately19:54:03
@raitobezarius:matrix.orgraitobezariusand it can cancel many builds in-between if failure occur19:54:13
@raitobezarius:matrix.orgraitobezarius

though my priority queue for CI infra is:

  • merge queue
  • macOS capacity
  • benchmarking infra
19:54:34
@raitobezarius:matrix.orgraitobezariusI cannot touch besadii for October19:54:47
@piegames:flausch.socialpiegamesI agree on the first two, can besadii be put over benchmarking infra?19:58:15

Show newer messages


Back to Room ListRoom Version: 10