| 17 Oct 2022 |
 Artturin | ci passed | 18:03:23 |
| 22 Oct 2022 |
 @zseri:matrix.org | huh, why does https://github.com/NixOS/nixpkgs/pull/190730/checks?check_run_id=9036063946 get marked as "neutral" instead of "failure/error" (one of the modified packages itself failed to compile)? | 11:47:03 |
 7c6f434c | Build failures are always reported as neutral outcomes, because failures are for things that are even more unambiguous (you'd need to check for disk full, transient network issues etc. to be sure about build failures) | 11:48:23 |
 Sandro | No, it is stupid. GitHub treats it as being ignorable which it often isn't and broken packages should be marked as such. | 13:05:34 |
| @zseri:matrix.org | In reply to @7c6f434c:nitro.chat
Build failures are always reported as neutral outcomes, because failures are for things that are even more unambiguous (you'd need to check for disk full, transient network issues etc. to be sure about build failures) like, you need to check for that anyways on failures, and failures just say "well, it failed (probably to compile)", but you can ignore it if it is a false-positive... | 13:37:53 |
| 7c6f434c | ofBorg is tuned carefully to minimise false-positive red-failures | 13:38:44 |
| @zseri:matrix.org | uhm but when does it report red-failures then? | 13:41:00 |
| @zseri:matrix.org | * uhm but when does it report red-failures then? only syntax-errors? | 13:41:18 |
| 7c6f434c | Failed eval, for example | 13:41:24 |
| 7c6f434c | It's more than syntax errors | 13:41:36 |
| @zseri:matrix.org | well, as you now need to check it anyways when it returns "neutral", I don't think that distinction is that useful. | 13:46:27 |
| Sandro | also github collapses the checks when they are green and neutral only | 22:39:37 |
| 23 Oct 2022 |
|  Ryan Burns changed their display name from Ryan Burns to r-burns. | 19:48:41 |
| 31 Oct 2022 |
|  @tinybronca:sibnsk.net changed their display name from underpantsgnome! to underpantsgnome. | 20:20:14 |
| 1 Nov 2022 |
| Artturin | cole-h: good job re https://github.com/NixOS/ofborg/commit/f7b2c00dae7ad57cc4164ed7dec42f447e98459e
https://github.com/NixOS/ofborg/pull/590 can be closed
| 18:46:45 |
| 7 Nov 2022 |
| Artturin | needs review/merge https://github.com/NixOS/ofborg/pull/618 | 21:48:02 |
| Artturin | https://github.com/NixOS/ofborg/pull/621 | 22:01:39 |
| 9 Nov 2022 |
 cole-h | Witnessed -- a bit slammed on time this week, but I'll see if I can't get those merged and deployed before next week. Sorry for the delay 🙇♂️ | 17:00:44 |
| 10 Nov 2022 |
|  teto joined the room. | 10:41:13 |
| teto | there is a "no space left on device" error when running this check https://logs.nix.ci/?key=nixos/nixpkgs.196945&attempt_id=b00ff29e-0e8b-4359-9494-36fb32c0f435 . Anything to be done or it's already fixed maybe ? | 10:41:49 |
| cole-h | Should have already been fixed. Try telling ofborg to build again and ping me if it happens again? | 15:22:22 |
| 13 Nov 2022 |
| cole-h | In reply to @artturin:matrix.org
needs review/merge https://github.com/NixOS/ofborg/pull/618 Finally getting around to redeploying ofborg with the updates, thanks again, and hopefully nothing goes wrong 😆 | 16:06:43 |
| 14 Nov 2022 |
 hexa | https://github.com/NixOS/nixpkgs/pull/131475 ofborg choked | 10:23:45 |
| cole-h | In reply to @hexa:lossy.network
https://github.com/NixOS/nixpkgs/pull/131475 ofborg choked Thanks -- just the ever-present incomplete API response, it seems. | 15:46:35 |
| hexa | cool! | 15:46:46 |
| hexa | webhooks are first to go when they have load issues 🙂 | 15:46:59 |
| 15 Nov 2022 |
| Artturin | https://github.com/NixOS/ofborg/pull/624 | 12:40:07 |
| Artturin | finally :D | 12:47:56 |
| 16 Nov 2022 |
|  @omlet:matrix.org joined the room. | 20:34:18 |
| 19 Nov 2022 |
 Winter (she/her) | anyone happen to know what's up with this? https://github.com/NixOS/nixpkgs/pull/200470#issuecomment-1320975891 | 21:46:25 |
