| 30 Oct 2023 |
 Hubble the Wolverine (they/them) | Oh I need to rebase I think | 04:51:58 |
|  Anthony Rsl joined the room. | 17:04:25 |
| 1 Nov 2023 |
|  cafkafk left the room. | 10:42:47 |
|  Ramses 🇵🇸 changed their display name from Ramses to Ramses 🇵🇸. | 19:58:24 |
| 2 Nov 2023 |
 7c6f434c | Hm, how to interpret «Complete, with errors» without details for ofborg-eval? | 07:23:06 |
| 7c6f434c | ofborg-eval-darwin complains about crashed Nix daemon (ENOENT on a socket) though | 07:23:38 |
| 10 Nov 2023 |
|  Luke joined the room. | 05:58:55 |
| Luke | Is there a way to check where a particular build request from a given PR is in the queue? I don’t know enough about Prometheus to know if this is feasible or to construct this query myself | 06:02:20 |
 hexa | no, that information is not available | 11:12:13 |
| Luke | Okay, in that case are there any timestamps within the logs or ways to correlate builds triggered from a PR to when they happened or what the inputs were? I’m trying to get something building on Darwin and without timestamps I can’t tell which run was the latest? | 14:27:14 |
 Artturin | force pushing will clear the actions | 14:28:30 |
| Artturin | * force pushing will clear the actions, maybe commits will too | 14:28:49 |
