 | Exotic Nix Targets | 319 Members |
| 96 Servers |
| Exotic Nix Targets | 319 Members |
| 96 Servers |
| Sender | Message | Time |
|---|---|---|
| 13 Jul 2023 | ||
 artemis | actually here is my whole `emerge --info` https://dpaste.com/22NWU74FE while i am at it | 09:05:52 |
 @trofi:matrix.org | I'll try to reproduce locally and if I fail we'll try to compare the build logs for difference. | 09:15:05 |
| @trofi:matrix.org | Built file locally for me: https://bpa.st/raw/SI6ZU. What log do you get with $ nix build --no-link github:NixOS/nixpkgs/9af373a61647257d16ae6062cddaa9094d24920c#pkgsCross.riscv64.libtool? | 10:11:29 |
| artemis | In reply to @trofi:matrix.orghttp://dpaste.com/6SMJ92MK9 | 20:11:15 |
 zuckerberg changed their profile picture. | 22:03:45 | |
| @trofi:matrix.org | Ended up being a libtool deficiency (current unstable is less unstable): https://github.com/NixOS/nixpkgs/pull/167071#issuecomment-1634992962 | 22:24:18 |
 sorear joined the room. | 23:48:33 | |
| 14 Jul 2023 | ||
| sorear | is useLLVM a topic for here? i've been trying to get it to work with current llvm, with mixed results | 00:09:28 |
 emilytrau | sorear: would you tell us more about what you're trying to do? :) | 09:52:57 |
| emilytrau | and what issues you're running into | 09:54:00 |
| emilytrau | Redacted or Malformed Event | 11:13:58 |
 p14 joined the room. | 11:19:17 | |
| p14 | On aarch64-linux, pkgsCross.musl64.pkgsStatic.stdenv stopped being a cache hit sometime around the 26th of May. Sha eb5cd54d0 looks to be the first commit at which it is missing on the nixos-23.05 branch, but the non cross stdenv also broke/stopped being a cache hit then by the looks of things. Does anyone have any idea why it might have gone missing and can we bring it back… ? I would also like to have the equivalent, but from x86 to aarch64 cross. | 11:19:29 |
 Alex | In reply to @p14:matrix.org Have you tried building it yourself or looking at the job status on Hydra? Usually, cache misses imply a failed build. | 11:20:20 |
| p14 | Funny, you should ask, I left it running for the last 15 minutes and it just finished successfully. | 11:20:50 |
| p14 | In reply to @alex:tunstall.xyzSo it does look like it builds but is missing for some other reason. What bit of the hydra infrastructure would cause it to become a cache hit ordinarily? | 11:21:48 |
 @rick:matrix.ciphernetics.nl changed their display name from Rick (Mindavi) to Mindavi. | 11:22:17 | |
| Alex | In reply to @p14:matrix.org A successful build. Everything Hydra builds is cached. So either Hydra lost the need to build it to build its jobs (due to job changes or failed evaluation), or your local build of the package doesn't have the same derivation as that built by Hydra. | 11:24:41 |
| p14 | I’m only building nixpkgs unmodified from upstream, No overlays or anything like that. I’m wondering if hydra stopped needing to build it? How would I tell what pulled it into the hydra build when it was working, and then look for that in today’s state? | 11:26:17 |
| p14 | Unfortunately the standard stdenv also stopped being a cache hit for a while around a similar time. I tried doing a git bisect where I skip commits if the ordinary standard environment does not build. Unfortunately, this points at a large set of commits including merges from staging. | 11:27:43 |
| Alex | In reply to @p14:matrix.orgI'd probably bisect until I find the exact commit where Hydra stopped building it, then look at what changed and how it affects the build closure using nix why-depends --derivation. | 11:27:48 |
| p14 | The commit pointed to by the bisect is the binutils patch (sha mentioned above), which is suspicious. But that requires rebuilding quite a bit of stuff. | 11:30:23 |
| Alex | FWIW stdenv depends on binutils | 11:31:01 |
| p14 | (That is, a bisect without skipping bad ordinary stdenvs) | 11:31:07 |
| p14 | Yeah, the fact that commit is not a hit makes me wonder if something else went wrong? I suppose with the periodic rebuilds it could be anything between that commit and the next commit built by hydra? How would I figure out which commits were built by hydra so I can look at them? | 11:32:18 |
| Alex | Hydra builds practically every commit. Look in the "inputs" tab for each evaluation. The evaluations list also shows whenever an input changes version. | 11:33:43 |
| p14 | I am struggling to understand how Hydra built this derivation. I am looking at the release 2305 nixos jobset, and the oldest thing there. I searching for pkgsStatic does show something up, but not pkgsCross. | 11:40:10 |
| @trofi:matrix.org | I would guess that only cross-trunk jobset from https://hydra.nixos.org/project/nixpkgs#tabs-project would build cross-compilers. | 15:06:19 |
| @trofi:matrix.org | It might be that you were lucky to try 23.05 when it was very close to trunk when binaries lied around. But I could completely misinterpret it as well. | 15:07:10 |
| @trofi:matrix.org | And looking at https://hydra.nixos.org/jobset/nixpkgs/cross-trunk there was a severe regression ~today: we lost 812 extra jobs. | 15:09:48 |