| 16 Jul 2023 |
 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 |
| @kranzes:matrix.org | The ofborg infra is different than the hydra one right? | 17:06:22 |
| @kranzes:matrix.org | not the same computing power I assume | 17:06:29 |
 raitobezarius | yes it's different | 17:09:55 |
| 7c6f434c | There are like 2 runners for aarch64-linux, I think | 17:10:57 |
| @kranzes:matrix.org | this is aarch64-dawrin | 17:11:20 |
| @kranzes:matrix.org | linux one is fine | 17:11:26 |
| 7c6f434c | Oops, sorry, yes | 17:11:33 |
| @kranzes:matrix.org | aarch64-darwin has always been impressively slow | 17:11:41 |
