!sBfrWMVsLoSyFTCkNv:nixos.org

OfBorg

168 Members
Number of builds and evals in queue: <TBD>60 Servers

Load older messages


SenderMessageTime
7 Jun 2022
@qyliss:fairydust.spaceAlyssa Ross in fact, as soon as stuff like with is involved, I'd assume it would be undecidable 15:30:03
@sandro:supersandro.deSandrohmmm... you're probably right. Would be cool if we could find a way around this15:31:01
@qyliss:fairydust.spaceAlyssa RossI think what we're looking for is coverage checking 15:31:39
@qyliss:fairydust.spaceAlyssa Rossbut I think that would have to be integrated into Nix15:31:53
@qyliss:fairydust.spaceAlyssa Rossthen you could see that these lines aren't evaluated by OfBorg, and try to add something that would evaluate them15:32:13
@sandro:supersandro.deSandrothat would be really useful 15:32:29
@7c6f434c:nitro.chat7c6f434c Rest assured it is undecidable even without with whether a line of code is dead or not… Coverage tracker sounds useful, yes. I wonder what fraction of the dead code would come from optional feature flags never set in Nixpkgs, of course. 19:48:49
@robert:funklause.dedotlambdaofborg also didn't flag the usage of an alias in https://github.com/NixOS/nixpkgs/pull/17673421:29:02
9 Jun 2022
@robert:funklause.dedotlambdaofborg didn't flag the usage of an alias in https://github.com/NixOS/nixpkgs/pull/175637 but nixpkgs-review does detect it00:13:06
@sandro:supersandro.deSandro*I think nixpkgs-review only uses it for one eval and it is a bit buggy07:37:21
@sandro:supersandro.deSandroBest to turn aliases of in config. Nix07:37:21
21 Jun 2022
@ncfavier:matrix.orgncfavier running @ofborg test networking wireguard gives instant success with a weird 404 log, while @ofborg build nixosTests.networking nixosTests.wireguard is fine 21:13:21
@ncfavier:matrix.orgncfavier @ofborg test networking.networkd.dhcpSimple is fine so it's probably a problem with attrsets 21:15:13
@ncfavier:matrix.orgncfavierlooks like https://github.com/NixOS/ofborg/issues/50421:18:30
22 Jun 2022
@hexa:lossy.networkhexaindeed, ofborg seems to be behaving weirdly for tests šŸ˜•14:34:21
@hexa:lossy.networkhexamany queued jobs, all unfinished14:35:50
25 Jun 2022
@sandro:supersandro.deSandroofborg logs are currently not loading for me22:25:59
@sandro:supersandro.deSandrothe websocket is only sending empty 1 bytes messages after the subscribe 22:26:46
27 Jun 2022
@tinybronca:sibnsk.nettinybronca joined the room.08:21:13
28 Jun 2022
@ma27:nicht-so.sexyma27 changed their profile picture.11:38:05
29 Jun 2022
@sandro:supersandro.deSandroHow did it happen that we lose aarch64-darwin?12:28:04
@qyliss:fairydust.spaceAlyssa Ross hmm, OfBorg doesn't seem to be noticing my @OfBorg build comments here https://github.com/NixOS/nixpkgs/pull/179556#issuecomment-1170407607 20:17:29
7 Jul 2022
@winterqt:nixos.devWinter (she/her)Is there a reason that failures during test eval are reported as neutral and not failing?04:17:39
@7c6f434c:nitro.chat7c6f434cYes. 04:18:02
@7c6f434c:nitro.chat7c6f434cThere are flaky tests, failed-before-anyway, disk full issues, timeouts…04:18:49
@7c6f434c:nitro.chat7c6f434c(also complicated issues with some subset of the builders…)04:19:26
@7c6f434c:nitro.chat7c6f434cEquating this to eval failures dilutes the clear «oops» status of reported definite-failures04:20:31
@winterqt:nixos.devWinter (she/her)
In reply to @7c6f434c:nitro.chat
Equating this to eval failures dilutes the clear «oops» status of reported definite-failures
Wait, just to be clear: actual failures during a test run are reported as failures, just not eval errors? Or are they all reported as neutral?
04:22:55
@7c6f434c:nitro.chat7c6f434cevail failures are failures 04:23:20
@7c6f434c:nitro.chat7c6f434cbuild/test failures are neutral04:23:28

Show newer messages


Back to Room ListRoom Version: 6