GHC in core-updates

GHC in core-updates

[Andreas Enge]

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'.

Re: GHC in core-updates

[Lars-Dominik Braun]

Hello Andreas,

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

I tried to compile GHC on core-updates recently, but didn’t even get
to GHC 9.2.5, because python2 failed to build (test test_asyncore failed,
without any further information). Do you have any extra patches applied?

Cheers,
Lars

Re: GHC in core-updates

[Andreas Enge]

Hello Lars,

Am Thu, Mar 09, 2023 at 01:45:54PM +0100 schrieb Lars-Dominik Braun:
> I tried to compile GHC on core-updates recently, but didn’t even get
> to GHC 9.2.5, because python2 failed to build (test test_asyncore failed,
> without any further information). Do you have any extra patches applied?

I did not change anything, my goal was just to try, with the tip of core-updates,
   ./pre-inst-env guix package -u
to see if any of my packages fail to build. I just checked, I have python2.
Maybe you had a transient test failure? "async" sounds like the kind of
tests that could fail randomly...

Andreas

Re: GHC in core-updates

[Andreas Enge]

But I confirm that ghc@9.2.5 now fails its tests, it has happened a second
time for me. Nothing in the recent commits to core-updates since I tried
the last time springs to mind as obviously having a connection to these
failures.

Andreas

Re: GHC in core-updates

[Lars-Dominik Braun]

Hi Andreas,

> But I confirm that ghc@9.2.5 now fails its tests, it has happened a second
> time for me. Nothing in the recent commits to core-updates since I tried
> the last time springs to mind as obviously having a connection to these
> failures.

fixed by commit ec79901a33b6463ad77dcaf4c37e538645b4d7b5 on
core-updates. I also verified pandoc builds.

Cheers,
Lars

Re: GHC in core-updates

[Andreas Enge]

Am Sun, Mar 12, 2023 at 05:26:51PM +0100 schrieb Lars-Dominik Braun:
> > But I confirm that ghc@9.2.5 now fails its tests
> fixed by commit ec79901a33b6463ad77dcaf4c37e538645b4d7b5 on
> core-updates. I also verified pandoc builds.

Wow, fantastic, thanks a lot!

Andreas

Re: GHC in core-updates

[Lars-Dominik Braun]

Hello Andreas,

> Maybe you had a transient test failure? "async" sounds like the kind of
> tests that could fail randomly...

unfortunately it is not a transient failure. I can reproduce it every
time I try to build python2 on core-updates, even with `--cores=1`.
And it also reproduces on master.

But, now that I have upgraded to kernel 6.1.12 it works. So I’m assuming
it might have been something like [1]. Building up to GHC 9.2.5 might
take a while though…

Cheers,
Lars

[1] https://discuss.python.org/t/linux-kernel-6-0-16-6-0-18-breaking-python-tests-allows-to-bind-a-socket-twice/22701