| 16 Jul 2023 |
 Lily Foster | You can replicate this one particular issue with nix-env --query --available --no-name --attr-path --out-path --option extra-experimental-features no-url-literals -f . -A stdenv yourself though (no obscenely large amount of RAM required)
I am admittedly just guessing though since running ofborg one-off is still not currently supported and I'm just manually running the nix commands that it does and inspecting code
| 11:22:36 |
| Lily Foster | (cole just seems to be out for the next few weeks, so I figured I'd help a bit since I'm not sure who else would be able to get ofborg logs) | 11:23:00 |
 piegames | Does ofborg automatically remove the "internal error" label or should I do it manually? | 14:09:53 |
 @rick:matrix.ciphernetics.nl | It does remove it automatically, if it stays then the ofborg maintainer will sometimes have a look at the related logs | 14:12:25 |
 Artturin | In reply to @rick:matrix.ciphernetics.nl
It does remove it automatically, if it stays then the ofborg maintainer will sometimes have a look at the related logs It's not removed automatically | 14:34:01 |
| Artturin | Never seen it happen | 14:34:49 |
| @rick:matrix.ciphernetics.nl | Hmm | 15:02:49 |
| @rick:matrix.ciphernetics.nl | At lease Cole said he'd like it if they are kept, not sure about autoremoval otherwise | 15:03:14 |
 7c6f434c | I have assumed the label is treated as «an open OfBorg issue» with removal triggered manually | 15:06:12 |
 Sandro 🐧 | So, when do we turn failed checks red instead of grey? | 22:15:37 |
| 17 Jul 2023 |
| Artturin | Maybe we could try it on non-staging PRs and see what issues come up | 01:24:03 |
|  trofi left the room. | 06:09:53 |
| 18 Jul 2023 |
| 7c6f434c | Is there any code deployed that tracks timeout/transient failures (network, ENOSPC)/dep failures/direct failures? Maybe its output should be the last line of failure log? It would be useful on its own when build logs are numerous enough for confusion, and without such code red checks are a glaringly obvious bad idea | 08:06:00 |
| Sandro 🐧 | It would probably already be enough if the logs wouldn't be combined | 08:53:20 |
| 7c6f434c | Properly choosing best last ten lines for a lots-of-small-stuff build is hard, a summary of which kinds of failures were present is useful, and it's a clear prerequisite for red checks anyway | 08:55:00 |
| Sandro 🐧 | Last x lines are not always useful, eg pytest shows the failure summary there which is usually not enough to provide anything other than that failed | 08:56:54 |
| 7c6f434c | For a single build at least you know it is a pytest failure… | 08:58:09 |
| @rick:matrix.ciphernetics.nl | In reply to @7c6f434c:nitro.chat
Is there any code deployed that tracks timeout/transient failures (network, ENOSPC)/dep failures/direct failures? Maybe its output should be the last line of failure log? It would be useful on its own when build logs are numerous enough for confusion, and without such code red checks are a glaringly obvious bad idea I don't think so | 17:50:55 |
| 19 Jul 2023 |
|  @kranzes:matrix.org joined the room. | 11:12:15 |
| @kranzes:matrix.org | Hi, I'm trying to figure out what (and why?) is ofboring doing for over 25 hours when it's not even building a package because it's for Linux only and that ofborg runner is Darwin. | 17:03:16 |
| @kranzes:matrix.org | https://github.com/NixOS/nixpkgs/pull/244160/files | 17:03:23 |
| @kranzes:matrix.org | 
Download image.png | 17:03:49 |
| @kranzes:matrix.org | * Hi, I'm trying to figure out what (and why?) is ofboring doing for over 27 hours when it's not even building a package because it's for Linux only and that ofborg runner is Darwin. | 17:04:01 |
| @rick:matrix.ciphernetics.nl | Trying to find out that it won't eval on Darwin... | 17:04:30 |
| @kranzes:matrix.org | and why does it take over a day? | 17:04:51 |
| @kranzes:matrix.org | x86_64-darwin went pretty fast, aarch64-darwin on the other hand... | 17:05:35 |
| Artturin | because the builders are overloaded | 17:05:38 |
| Artturin | * probably because the builders are overloaded | 17:05:41 |
| Artturin | * probably because the builders have a big queu | 17:06:07 |
| Artturin | also possible it's just stuck | 17:06:12 |
