| 29 Jul 2023 |
 implr | it's nix (not nixos) on gentoo amd64, so far from standard | 20:15:32 |
 trofi | might be a missing underlying filesystem feature? | 21:15:51 |
| trofi | which package you are trying to build out of curiosity? maybe if fails for me as well | 21:16:27 |
 artemis | im running a build of `nixos-cross-image-efi` on my gentoo amd64 ill let you know if it fails | 23:37:39 |
| 30 Jul 2023 |
| artemis | trofi: i also got an error in the check phase, http://dpaste.com/9RB3YHUA3
I'm building `nix build github:misuzu/nixos-vf2#nixos-cross-image-efi` without the flake's cache enabled | 02:09:49 |
| artemis | in case you want to try and reproduce as well | 02:09:57 |
| artemis | I ran that without anything added to my sandbox.
im re-running with `qemu-riscv64` added to my sandbox to see if this is another one of those things of enabled binfmts leaking into the sandbox and causing things to think it has an elf interpreter for an executable when that interpreter isn't actually on PATH like the other issue we were seeing | 02:12:35 |
| artemis | be back in a bit | 02:12:55 |
| artemis | ok i get the failure all the same so it's probably not related to the binfmts at least | 02:15:55 |
| artemis | implr: to confirm, is that error log i linked above showing a failure on the same test yours fails on? | 02:26:38 |
 Alex | I left mine running overnight and have gotten a failure in psutil:
psutil> =================================== FAILURES ===================================
psutil> _______________________ TestMemoryAPIs.test_swap_memory ________________________
psutil>
psutil> self = <psutil.tests.test_system.TestMemoryAPIs testMethod=test_swap_memory>
psutil>
psutil> def test_swap_memory(self):
psutil> mem = psutil.swap_memory()
psutil> self.assertEqual(
psutil> mem._fields, ('total', 'used', 'free', 'percent', 'sin', 'sout'))
psutil>
psutil> assert mem.total >= 0, mem
psutil> assert mem.used >= 0, mem
psutil> if mem.total > 0:
psutil> # likely a system with no swap partition
psutil> > assert mem.free > 0, mem
psutil> E AssertionError: sswap(total=8204054528, used=8204054528, free=0, percent=100.0, sin=35428151296, sout=75186987008)
psutil> E assert 0 > 0
psutil> E + where 0 = sswap(total=8204054528, used=8204054528, free=0, percent=100.0, sin=35428151296, sout=75186987008).free
psutil>
psutil> /nix/store/f43p2hab6y6hqqmlnyp6c61cx2kslifx-python3.10-psutil-5.9.5/lib/python3.10/site-packages/psutil/tests/test_system.py:298: AssertionError
psutil> =========================== short test summary info ============================
psutil> FAILED ../../nix/store/f43p2hab6y6hqqmlnyp6c61cx2kslifx-python3.10-psutil-5.9.5/lib/python3.10/site-packages/psutil/tests/test_system.py::TestMemoryAPIs::test_swap_memory - AssertionError: sswap(total=8204054528, used=8204054528, free=0, percent=10...
psutil> ============ 1 failed, 26 passed, 1 skipped, 16 deselected in 0.63s ============
psutil> /nix/store/ld7x5as7sc5sbzmhzh6s6s9jfksil1h4-stdenv-linux/setup: line 1596: pop_var_context: head of shell_variables not a function context
error: builder for '/nix/store/24sg1zbm3wq2h8nv68jivynlmhmllnb9-python3.10-psutil-5.9.5.drv' failed with exit code 1;
This is quite possibly a bug in psutil's test suite where it fails when at 100% swap usage. | 03:20:14 |
| trofi | yeah, psutil failure looks related to RAM usage.
| 06:42:49 |
| trofi | coreutils' mv-i test looks simple: https://github.com/coreutils/coreutils/blob/master/tests/mv/i-1.pl . I wonder why it printed help banner. Aaaand I reproduced it in gentoo chroot as well \o/: $ nix build nixpkgs#coreutils --rebuild. | 06:53:26 |
| implr | In reply to @artemis:arty.chat
implr: to confirm, is that error log i linked above showing a failure on the same test yours fails on? yep, same | 10:43:20 |
| implr | and it actually fails on native (sufficiently new) nixpkgs for me as well, so the problem is just coreutils9.3, not riscv/cross compile related | 10:43:56 |
| Alex | In reply to @implr:hackerspace.pl
and it actually fails on native (sufficiently new) nixpkgs for me as well, so the problem is just coreutils9.3, not riscv/cross compile related Not every coreutils 9.3 fails on native.
I have a working RV64GC_Zba_Zbb build on 23.11.git.7c67f006ea0M without any overrides (besides the custom GCC 13 stdenv). | 10:46:31 |
|  patryk4815 joined the room. | 21:50:30 |
| 31 Jul 2023 |
|  Yingchi Long changed their profile picture. | 18:15:45 |
|  Charles joined the room. | 22:02:53 |
|  @machinaut:matrix.org left the room. | 22:40:26 |
| 1 Aug 2023 |
| Charles changed their profile picture. | 01:12:22 |
 p14 | Download usellvm-16.patch | 14:04:38 |
| p14 | I managed to get pkgsLLVM.nix working with an import <nixpkgs> { overlays = [(self: super: { llvmPackages = self.llvmPackages_16; })]; } overlay; however, I did have fix a few other minor things (libseccomp doCheck = false; lowdown hardeningDisable fortify; boost NIX_CFLAGS_LINK = prev.NIX_CFLAGS_LINK + " --target=${self.stdenv.hostPlatform.config}";, and disable 3 tests from nix) | 14:06:30 |
| p14 | raitobezarius: any thoughts on the above patch? I'm on x86_64-unknown-linux-gnu, I have the impression you primarily were trying to make a darwin platform work | 14:07:10 |
| p14 | I've commented the hacks so hopefully the motivation might be clear. Do you think this is suitable to send as a patch to make llvmPackages_16 work? | 14:07:38 |
| p14 | [apols, I have to run away for a few hours shortly] | 14:07:55 |
 raitobezarius | I'd say open a PR, expose the problem solved by this and tag the LLVM maintainers | 14:08:00 |
| raitobezarius | it's hard to review like this stuff | 14:08:06 |
| p14 | raitobezarius: which branch do I send it for -- is master OK given that little will depend directly on llvmPackages_16? | 14:12:27 |
| raitobezarius | master is fine | 14:12:56 |
