Here is my 'guix describe' output for reference:

--8<---------------cut here---------------start------------->8---
  asahi df2f53d
    repository URL: https://codeberg.org/asahi-guix/channel
    branch: main
    commit: df2f53d4f19e0549eab02841870e127d5d9e7963
  guix 19453a8
    repository URL: https://git.guix.gnu.org/guix.git
    branch: master
    commit: 19453a8a9f75b8bd4c62b5479839c4c47d4ad30a
  guix-rust-past-crates b8b7ffb
    repository URL: https://codeberg.org/guix/guix-rust-past-crates.git
    branch: trunk
    commit: b8b7ffbd1cec9f56f93fae4da3a74163bbc9c570
--8<---------------cut here---------------end--------------->8---

When trying to build [email protected] for aarch64-linux (on Apple M1 Pro), I get a 
build failure. When investigating the logs, all tests pass except one:

--8<---------------cut here---------------start------------->8---
121/545 Test #121: tst_qlatin1stringmatcher 
..............................***Failed    1.43 sec
********* Start testing of tst_QLatin1StringMatcher *********
Config: Using QtTest library 6.9.2, Qt 6.9.2 (arm64-little_endian-lp64 shared 
(dynamic) release build; by GCC 14.3.0), unknown unknown
PASS   : tst_QLatin1StringMatcher::initTestCase()
PASS   : tst_QLatin1StringMatcher::overloads()
PASS   : tst_QLatin1StringMatcher::staticOverloads()
PASS   : tst_QLatin1StringMatcher::staticOverloads_QStringViewHaystack()
PASS   : tst_QLatin1StringMatcher::interface()
PASS   : tst_QLatin1StringMatcher::indexIn()
QDEBUG : tst_QLatin1StringMatcher::haystacksWithMoreThan4GiBWork() created 
dataset in 221 ms
CMake Error at tst_qlatin1stringmatcherWrapperRelWithDebInfo.cmake:18 (message):
  
  
/tmp/guix-build-qtbase-6.9.2.drv-0/build/tests/auto/corelib/text/qlatin1stringmatcher/tst_qlatin1stringmatcher
  execution failed with exit code Subprocess killed.
--8<---------------cut here---------------end--------------->8---

I found a loosely related issue on Codeberg 
(https://codeberg.org/guix/guix/issues/550), but that issue seems to be when 
building with QEMU specifically (and the test failures were different.) 

I know very little about the package build process, and wanted to check to see 
if I am doing something wrong before opening an issue. If there is anything 
else in the build logs that might be useful, I would be happy to provide it if 
pointed in the right direction, but the logs are too large to share in full.

Kind Regards,

Graysen Pitts

Reply via email to