| 29 Oct 2023 |
 K900 | https://github.com/NixOS/nixpkgs/pull/263768 broke eval of the package on aarch64 | 19:53:10 |
| K900 | But the check is green, because the other package evaluated and built | 19:53:18 |
| 30 Oct 2023 |
 Hubble the Wolverine (they/them) | I'm getting an interesting failure on https://github.com/NixOS/nixpkgs/pull/264292
error: evaluation aborted with the following error message: 'Failed to evaluate libhugetlbfs-2.23: «unknown-meta»: has an invalid meta attrset:
- key 'meta.badPlatforms' has invalid value; expected list of (string or attribute set of anything), got
is this a known one? I think I saw it in #dev:nixos.org before...
| 04:43:27 |
| Hubble the Wolverine (they/them) | In reply to @hubofeverything:bark.lgbt
I'm getting an interesting failure on https://github.com/NixOS/nixpkgs/pull/264292
error: evaluation aborted with the following error message: 'Failed to evaluate libhugetlbfs-2.23: «unknown-meta»: has an invalid meta attrset:
- key 'meta.badPlatforms' has invalid value; expected list of (string or attribute set of anything), got
is this a known one? I think I saw it in #dev:nixos.org before...
I'm assuming it's related to https://github.com/NixOS/nixpkgs/pull/264290 | 04:49:31 |
| 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 |
| Artturin | * commit/force push to clear the actions | 14:29:04 |
| Luke | In reply to @artturin:matrix.org
force pushing will clear the actions Yeah, but the old logs still show up on ofborg.org? | 14:38:21 |
 Lily Foster | In reply to @luke:vuksta.com
Yeah, but the old logs still show up on ofborg.org? the github checks link to the specific build when they are done | 14:43:38 |
| 11 Nov 2023 |
|  NinjaTrappeur left the room. | 07:14:32 |
| 13 Nov 2023 |
|  @raboof:matrix.org left the room. | 08:51:17 |
| 14 Nov 2023 |
 cole-h | FYI: ofborg may or may not be down at the moment -- I can't ssh into the machines, ofborg-core can't scrape any of the evaluators/builders, ~~but ofborg.org is still working (which is hosted on ofborg-core)~~ and ofborg.org (which is hosted on ofborg-core) is now unreachable 🤷
EM has an incident: https://status.equinixmetal.com/incidents/yv4h4jfjy3hq | 01:59:52 |
| cole-h | (It's been resolved, for the moment, it seems) | 02:04:12 |
| cole-h | * FYI: ofborg may or may not be down at the moment -- I can't ssh into the machines, ofborg-core can't scrape any of the evaluators/builders, but ofborg.org is still working (which is hosted on ofborg-core) and ofborg.org (which is hosted on ofborg-core) is now unreachable 🤷
EM has an incident: https://status.equinixmetal.com/incidents/yv4h4jfjy3hq | 02:04:19 |
| 15 Nov 2023 |
|  @grahamc:nixos.orgchanged room power levels. | 16:15:51 |
| @grahamc:nixos.org | 16:36:17 |
| @grahamc:nixos.org | 16:38:51 |
| @grahamc:nixos.org left the room. | 16:41:20 |
|  Alyssa Ross | 17:35:09 |
|  NixOS Moderation Botchanged room power levels. | 18:13:09 |
