OfBorg | 183 Members | |
| Number of builds and evals in queue: <TBD> | 64 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Jul 2023 | ||
| 12:31:12 | ||
| there are currently no and
https://ofborg.org/prometheus/graph?g0.expr=ofborg_queue_builder_consumers%7Barch!~%22._-lowprior%22%7D&g0.tab=0&g0.stacked=0&g0.show_exemplars=0&g0.range_input=1w&g1.expr=ofborg_queue_builder_waiting%7Barch!~%22._-lowprior%22%7D&g1.tab=0&g1.stacked=0&g1.show_exemplars=0&g1.range_input=1w | 14:55:37 | |
| * there are currently no and
edit: (attempt) at fixing the link | 15:10:43 | |
| 15:11:17 | ||
| 24 Jul 2023 | ||
| 15:45:00 | ||
| 15:46:07 | ||
| 25 Jul 2023 | ||
| 16:43:10 | ||
| 26 Jul 2023 | ||
| Silly question: how much work is it to make the «master fails to evaluate» state be «skipped» for (Ideally it would be «passed» if PR evaluates, but that probably needs a change to what gets evaluated in this case, so more work) | 16:45:00 | |
| It's a good indication that everything is broken, so I'm in favor of keeping it | 16:58:49 | |
| It gose against the core principle of ofBorg checks: red should not be merged | 16:59:43 | |
| Redacted or Malformed Event | 17:38:47 | |
| To clarify; this is for the use case where you make a PR that fixes an eval issue? | 17:46:07 | |
| I guess it's in scope, but it's also not the general case | 17:46:27 | |
| 18:20:13 | ||
| I'd rather say that red means that you should be careful about merging. I think that still applies at least partially, as some ofBorg checks can't even be done if master won't evaluate. | 18:50:55 | |
| (Though it's nothing against making the possible checks work instead of getting skipped.) | 18:51:58 | |
| 27 Jul 2023 | ||
| 03:03:59 | ||
| 31 Jul 2023 | ||
| 21:55:36 | ||
| 1 Aug 2023 | ||
| 14:15:05 | ||
In reply to @sandro:supersandro.deProbably at least somewhat related to evals up almost 100% over the last ~year, see my messages starting ~here: https://matrix.to/#/!sBfrWMVsLoSyFTCkNv:nixos.org/$L0IZji-evYLXfqLjemyARJdhDXZsae4eijFoACigOUQ?via=nixos.org&via=matrix.org&via=nixos.dev | 14:40:38 | |
In reply to @sandro:supersandro.de* Probably at least somewhat related to eval times being up almost 100% over the last ~year, see my messages starting ~here: https://matrix.to/#/!sBfrWMVsLoSyFTCkNv:nixos.org/$L0IZji-evYLXfqLjemyARJdhDXZsae4eijFoACigOUQ?via=nixos.org&via=matrix.org&via=nixos.dev | 14:45:38 | |
| 2 Aug 2023 | ||
| we have been seeing failing ofborg nixos test runs for kanidm for the last two releases, but noone could reproduce them locally https://github.com/NixOS/nixpkgs/pull/246564#issuecomment-1661845814 https://github.com/NixOS/nixpkgs/pull/229309#issuecomment-1571863333 | 12:24:43 | |
| seems always related to namespacing | 12:30:58 | |
| 3 Aug 2023 | ||
| 06:12:50 | ||
| 5 Aug 2023 | ||
| https://github.com/NixOS/ofborg/pull/642 | 21:29:40 | |
| 6 Aug 2023 | ||
| 17:08:21 | ||
| 7 Aug 2023 | ||
| 09:41:28 | ||
In reply to @artturin:matrix.orgI'll try to find some time to finally get that deployed this week -- been a bit busy recently 😅 | 14:52:45 | |
| 11 Aug 2023 | ||
| 07:50:18 | ||
| Hello A check for my github pr, "OfBorg / tcl, tcl.passthru.tests on aarch64-darwin", https://github.com/NixOS/nixpkgs/pull/243838 , has been stuck for three weeks now. I understand aarch64-darwin is overloaded, but is this kind of delay normal now? | 07:53:27 | |