!sBfrWMVsLoSyFTCkNv:nixos.org

OfBorg

164 Members
Number of builds and evals in queue: <TBD>59 Servers

Load older messages


SenderMessageTime
10 Jan 2022
@winterqt:nixos.devWinter (she/her)
In reply to @hexa:lossy.network
I don't believe there is a working sandbox on darwin
There definitely is (I have it enabled)
00:10:18
@winterqt:nixos.devWinter (she/her)But it’s not without its breakages00:10:25
@winterqt:nixos.devWinter (she/her) Is there any way that I can run OfBorg locally just to debug a specific task? (calculating changed attributes)
Or should I just do the things it does to do that manually, idk.
The latter is probably simpler
00:12:29
@winterqt:nixos.devWinter (she/her)(I know I asked a similar question earlier so I don’t know why I’m asking again, sorry.$00:13:08
@winterqt:nixos.devWinter (she/her)* (I know I asked a similar question earlier so I don’t know why I’m asking again, sorry.)00:13:12
@piegames:matrix.orgpiegames
In reply to @winterqt:nixos.dev
Is there any way that I can run OfBorg locally just to debug a specific task? (calculating changed attributes)
Or should I just do the things it does to do that manually, idk.
The latter is probably simpler
Ah, I found it https://github.com/NixOS/ofborg/pull/562 (FWIW)
00:16:46
@winterqt:nixos.devWinter (she/her)I’ll take a look, thanks.00:26:56
@winterqt:nixos.devWinter (she/her) So an issue that I ran into was that https://github.com/NixOS/nixpkgs/pull/153038#discussion_r780785733 (go to the last resolved discussion and expand it) didn’t cause OfBorg to detect myself as a maintainer. But I’m… not really sure why. I can successfully go into a REPL and see that thelounge.meta.maintainers exists.
Does anyone have any pointers on why this would be happening, or where to look in the codebase, or something?
00:29:16
@winterqt:nixos.devWinter (she/her) * So an issue that I ran into was that https://github.com/NixOS/nixpkgs/pull/153038#discussion_r780785733 (go to the last resolved discussion and expand it) didn’t cause OfBorg to detect myself as a maintainer (and add the by package maintainer label). But I’m… not really sure why. I can successfully go into a REPL and see that thelounge.meta.maintainers exists.
Does anyone have any pointers on why this would be happening, or where to look in the codebase, or something?
00:30:09
@winterqt:nixos.devWinter (she/her)Nothing immediately stands out to me :/00:32:51
@sternenseemann:systemli.orgsterni Winter (she/her): ofborg relies on the attribute names in the commit message mostly, so the PR wouldn't trigger that code because there's no thelounge: … commit, I would assume? 11:10:29
12 Jan 2022
@grahamc:nixos.org@grahamc:nixos.org I think “thelounge:” is only for triggering builds, not @ing maintainers. This is to encourage good commit message format, but still @ing relevant people even if the author didn’t do it quite right 14:33:27
@winterqt:nixos.devWinter (she/her)
In reply to @grahamc:nixos.org
I think “thelounge:” is only for triggering builds, not @ing maintainers. This is to encourage good commit message format, but still @ing relevant people even if the author didn’t do it quite right
I’m confused. You said it’s not for @ing but it would @ anyways?
14:38:37
@winterqt:nixos.devWinter (she/her)(I’ll reword my commits to use the actual attribute name, though; thanks for the clarification.)14:39:46
@winterqt:nixos.devWinter (she/her) *
In reply to @grahamc:nixos.org
I think “thelounge:” is only for triggering builds, not @ing maintainers. This is to encourage good commit message format, but still @ing relevant people even if the author didn’t do it quite right
I’m confused. You said it’s not for @ing but that it would @ anyways?
14:44:14
@grahamc:nixos.org@grahamc:nixos.org There is a rule that determines what things to build, and that rule is based on attribute as named in the commit message with the prefix. It has nothing to do with @ing people, iirc. 14:45:44
@winterqt:nixos.devWinter (she/her)Ah, understood.14:46:50
@sternenseemann:systemli.orgsterniyeah seems like that should use the changed attribute paths14:58:34
@ncfavier:matrix.orgncfavier joined the room.16:08:55
13 Jan 2022
@mjolnir:nixos.orgNixOS Moderation Bot unbanned @blaggacao:matrix.orgDavid Arnold (blaggacao).18:43:45
14 Jan 2022
@cw:kernelpanic.cafeChinchilla Washington changed their display name from Rev. CornWallace III (novus ordo seclorum) to coilWinder.04:39:47
@cw:kernelpanic.cafeChinchilla Washington changed their display name from coilWinder to CoilWinder (novus ordo seclorum).04:42:11
17 Jan 2022
@pennae:matrix.eno.spacepennaedoes ofborg not parse commands from review comments? https://github.com/NixOS/nixpkgs/pull/153346#pullrequestreview-854622718 apparently hasn't started a test run16:44:25
@7c6f434c:nitro.chat7c6f434cI would expect that review comments is a completely different kind of thing that Github peruidically breaks in a different way than comments (so probably ofBorg does not receive these events)16:46:14
@pennae:matrix.eno.spacepennaeannoying, but not entirely surprising16:47:51
@winterqt:nixos.devWinter (she/her)Do NixOS tests always have to be triggered manually?17:39:16
@winterqt:nixos.devWinter (she/her)I’ve never seen them run automatically for changed modules/tests.17:39:35
@hexa:lossy.networkhexathey run automatically if a package updated includes passthru.tests = [ inherit (nixosTest) foobar ];18:00:47
@hexa:lossy.networkhexa * they run automatically if a package updated includes passthru.tests = { inherit (nixosTest) foobar };18:00:56
@7c6f434c:nitro.chat7c6f434cPackage specified in the commit message, I think18:04:09

Show newer messages


Back to Room ListRoom Version: 6