all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: GHC in core-updates
Date: Thu, 9 Mar 2023 10:23:51 +0100	[thread overview]
Message-ID: <ZAmlpxTAczK2xHeo@jurong> (raw)

Hello,

the latest trial to compile ghc@9.2.5 resulted in many test errors,
see below.

Andreas


SUMMARY for test run started at Thu Mar  9 06:51:34 2023
2:19:05.987429 spent to go through
    8323 total tests, which gave rise to
   41557 test cases, of which
   29559 were skipped

      44 had missing libraries
    8597 expected passes
     105 expected failures

       0 caused framework failures
       0 caused framework warnings
       0 unexpected passes
       3 unexpected failures
       0 unexpected stat failures
      22 fragile tests

Unexpected failures:
   hsc2hs/T12504.run                    T12504 [bad stderr] (normal)
   simplCore/should_compile/T13340.run  T13340 [bad stderr] (normal)
   numeric/should_run/T7014.run         T7014 [bad stderr] (normal)

Fragile test passes:
   codeGen/should_run/cgrun057.run                 cgrun057 [fragile] (profasm)
   concurrent/prog001/concprog001.run              concprog001 [fragile] (threaded2)
   libraries/base/tests/CPUTime001.run             CPUTime001 [fragile] (normal)
   concurrent/should_run/foreignInterruptible.run  foreignInterruptible [fragile] (ghci)
   profiling/should_run/heapprof001.run            heapprof001 [fragile] (prof)
   profiling/should_run/heapprof001.run            heapprof001 [fragile] (prof_hb)
   profiling/should_run/heapprof001.run            heapprof001 [fragile] (prof_hc_hb)
   profiling/should_run/heapprof001.run            heapprof001 [fragile] (prof_hd)
   profiling/should_run/heapprof001.run            heapprof001 [fragile] (prof_hr)
   profiling/should_run/heapprof001.run            heapprof001 [fragile] (prof_hy)
   profiling/should_run/heapprof001.run            heapprof001 [fragile] (profasm)
   concurrent/should_run/hs_try_putmvar003.run     hs_try_putmvar003 [fragile] (threaded1)
   profiling/should_run/T15897.run                 T15897 [fragile] (profasm)
   profiling/should_run/T15897.run                 T15897 [fragile] (profasm)
   ghci/should_run/T3171.run                       T3171 [fragile] (normal)
   profiling/should_run/T5559.run                  T5559 [fragile] (ghci-ext-prof)
   profiling/should_run/T5559.run                  T5559 [fragile] (prof)
   profiling/should_run/T5559.run                  T5559 [fragile] (profasm)
   concurrent/should_run/T5611.run                 T5611 [fragile] (normal)
   concurrent/should_run/T5611a.run                T5611a [fragile] (normal)

Fragile test failures:
   runghc/T-signals-child.run  T-signals-child [fragile] (threaded1)
   ghci/linking/T11531.run     T11531 [fragile] (normal)

make[1]: *** [../mk/test.mk:356: test] Error 1
make[1]: Leaving directory '/tmp/guix-build-ghc-9.2.5.drv-0/ghc-9.2.5/testsuite/tests'
make: *** [Makefile:224: test] Error 2

Test suite failed, dumping logs.
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("test" "VERBOSE=4" "EXTRA_RUNTEST_OPTS=--skip-perf-tests") exit-status: 2 term-signal: #f stop-signal: #f>
phase `check' failed after 8351.8 seconds
command "make" "test" "VERBOSE=4" "EXTRA_RUNTEST_OPTS=--skip-perf-tests" failed with status 2
builder for `/gnu/store/yk5cggkmnacl98q7im7v9lni73vnh5sh-ghc-9.2.5.drv' failed with exit code 1
build of /gnu/store/yk5cggkmnacl98q7im7v9lni73vnh5sh-ghc-9.2.5.drv failed
View build log at '/var/log/guix/drvs/yk/5cggkmnacl98q7im7v9lni73vnh5sh-ghc-9.2.5.drv.gz'.



             reply	other threads:[~2023-03-09  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  9:23 Andreas Enge [this message]
2023-03-09 12:45 ` GHC in core-updates Lars-Dominik Braun
2023-03-09 14:08   ` Andreas Enge
2023-03-10 13:16     ` Andreas Enge
2023-03-12 16:26       ` Lars-Dominik Braun
2023-03-12 16:56         ` Andreas Enge
2023-03-10 17:47     ` Lars-Dominik Braun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZAmlpxTAczK2xHeo@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.