| 23 Aug 2023 |
 @asymmetric:matrix.dapp.org.uk | * ok. asking because i'm trying to document a list of supported platform tiers, and wondering where aarch64-darwin should be there.
From the perspective of OfBorg (and if you have the context, the POV of Hydra as well), do you agree with the following:
Tier 1
x86_64-linux-gnu using gcc
Tier 2
aarch64-linux using gccaarch64-darwin using clangx86_64-darwin using clang
| 15:15:27 |
 cole-h | I don't know the definitions of "tier X", so I can't really comment. | 15:15:49 |
| cole-h | From my perspective, they're all "best effort", with most of that "effort" concentrated on x86_64-linux-gnu :P | 15:16:10 |
| @asymmetric:matrix.dapp.org.uk | OK, that's more or less how I meant those tiers to be understood | 15:16:30 |
| @asymmetric:matrix.dapp.org.uk | But for a formal definition (which I don't think is being followed), see this merged RFC https://github.com/7c6f434c/rfcs/blob/platform-support-tiers/rfcs/0046-platform-support-tiers.md | 15:17:16 |
| @asymmetric:matrix.dapp.org.uk | * But for a formal definition (which I don't think is being followed), see this merged RFC https://github.com/NixOS/rfcs/pull/46 | 15:17:36 |
| cole-h | At least for ofborg, we do have more support for aarch64-linux as opposed to any of the darwin systems (mostly due to it being easier and cheaper to get high-powered machines for our builds) | 15:17:50 |
| cole-h | So, only taking ofborg's support into account, I'd order the "effort" for each platform as x86_64-linux > aarch64-linux >>>>>>> aarch64-darwin > x86_64-darwin | 15:18:49 |
 Lily Foster | Tbh my ofborg builds often finish on aarch64-linux box first, which is impressive given all of the runners are on the same massive community builder box | 15:24:39 |
| cole-h | Ampere is super stronk. And the x86_64-linux builders also run the evals (which are expensive), which may contribute to their relative slowness :P | 15:26:11 |
| Lily Foster | Oof, I didn't realize those were co-located on the same boxen 👀 | 15:27:35 |
| @asymmetric:matrix.dapp.org.uk | Opinions about this addition to the manual? https://github.com/NixOS/nixpkgs/commit/5cfe383bf142098570b89868262f81f1bb752a27?short_path=a156135#diff-a156135d5b3fa0cdcb3bcc1566d5ecb22929aaad47d03fc80013ef07f58ee918 | 16:09:22 |
| @asymmetric:matrix.dapp.org.uk | * Opinions about this planned addition to the manual? https://github.com/asymmetric/nixpkgs/blob/doc-support-tiers-redux/doc/stdenv/platform-support.chapter.md | 16:11:32 |
| 24 Aug 2023 |
| cole-h | No comment on the darwin section; linux section seems alright | 14:40:08 |
| 25 Aug 2023 |
|  @rover:aguiarvieira.pt joined the room. | 20:57:15 |
|  @adam:robins.wtf joined the room. | 20:58:21 |
| 28 Aug 2023 |
 Artturin | https://github.com/NixOS/ofborg/pull/642 | 14:53:36 |
| 29 Aug 2023 |
 @infinisil:matrix.org | Does ofborg do something where it re-uses a previous git tree? Because it looks like this run is including a file that isn't there anymore in the commit: https://github.com/NixOS/nixpkgs/pull/252154/checks?check_run_id=16325959723 | 22:40:20 |
| @infinisil:matrix.org | It mentions the case-sensitive-duplicate-package file, but the latest commit from that PR removed that file | 22:40:42 |
| @infinisil:matrix.org | Like it's missing a git clean | 22:41:18 |
| Lily Foster | It does do something like that, yeah. Let me look and see how ofborg cleans the tree | 22:45:52 |
| Lily Foster | Yeah, it looks like it only does operation aborts and a git reset --hard. Which when the file is removed obviously that won't do anything without a git clean -df (or -xdf) | 22:49:29 |
| Lily Foster | Trying to confirm if a dirty/untracked tree is what occurred at all though | 22:50:04 |
| Lily Foster | It looks like the previous x86_64-darwin build was on a different mac (macstadium-x86-44911507 vs macstadium-x86-44911362). Let me see how ofborg propagates those source files for the build | 22:52:52 |
| @infinisil:matrix.org | Lily Foster: Thanks for looking into it! it's very likely this is related to this directory having contained a duplicate case-sensitive directory entry before, maybe it does like a git checkout of the previous commit first, and then git has trouble cleaning up the duplicate file | 22:57:24 |
| @infinisil:matrix.org | Something like that | 22:57:31 |
| Lily Foster | Yeah something like that. I'm trying to replicate a history where a git reset between two commits will leave behind untracked (but previously tracked) files, to test | 22:59:47 |
| Lily Foster | Oh. I understand what you're saying now. Yeah git got confused by the combination of a case insensitive file-system and the clash | 23:12:19 |
| Lily Foster | So I can replicate this on the darwin builder checking out between those two commits. It leaves behind an empty dir, which is something git doesn't even consider | 23:15:41 |
| Lily Foster | It does look like a git clean -xdf does get it though | 23:15:55 |
