* CLISP test failures on ‘core-updates’
@ 2024-06-08 20:46 Ludovic Courtès
2024-06-08 21:55 ` Guillaume Le Vaillant
0 siblings, 1 reply; 4+ messages in thread
From: Ludovic Courtès @ 2024-06-08 20:46 UTC (permalink / raw)
To: glv, cox.katherine.e+guix, me, sharlatanus, jgart; +Cc: guix-devel
Hello Lisp team! :-)
The ‘clisp’ package has a few test failures on ‘core-updates’
(x86_64-linux):
--8<---------------cut here---------------start------------->8---
finished 57 files: 6 errors out of 11,960 tests
1 alltest: 0 errors out of 636 tests
2 array: 0 errors out of 290 tests
3 backquot: 0 errors out of 89 tests
4 bin-io: 0 errors out of 15 tests
5 characters: 0 errors out of 221 tests
6 clos: 0 errors out of 496 tests
7 defhash: 0 errors out of 6 tests
8 encoding: 0 errors out of 36 tests
9 eval20: 0 errors out of 50 tests
10 ext-clisp: 1 error out of 118 tests
11 ffi: 0 errors out of 263 tests
12 floeps: 0 errors out of 20 tests
13 format: 0 errors out of 307 tests
14 genstream: 0 errors out of 14 tests
15 hash: 0 errors out of 48 tests
16 hashlong: 0 errors out of 14 tests
17 hashtable: 0 errors out of 10 tests
18 iofkts: 0 errors out of 228 tests
19 lambda: 0 errors out of 90 tests
20 lists151: 0 errors out of 201 tests
21 lists152: 0 errors out of 255 tests
22 lists153: 0 errors out of 1 test
23 lists154: 0 errors out of 46 tests
24 lists155: 0 errors out of 25 tests
25 lists156: 0 errors out of 20 tests
26 list-set: 0 errors out of 10 tests
27 loop: 0 errors out of 151 tests
28 macro8: 0 errors out of 253 tests
29 map: 0 errors out of 64 tests
30 mop: 0 errors out of 225 tests
31 number: 0 errors out of 3,655 tests
32 number2: 0 errors out of 331 tests
33 pack11: 0 errors out of 211 tests
34 path: 0 errors out of 179 tests
35 readtable: 0 errors out of 27 tests
36 setf: 0 errors out of 197 tests
37 socket: 0 errors out of 92 tests
38 steele7: 0 errors out of 86 tests
39 streams: 2 errors out of 388 tests
40 streamslong: 1 error out of 25 tests
41 strings: 0 errors out of 409 tests
42 symbol10: 0 errors out of 152 tests
43 symbols: 0 errors out of 6 tests
44 time: 0 errors out of 22 tests
45 tread: 0 errors out of 395 tests
46 type: 0 errors out of 289 tests
47 unportable: 0 errors out of 31 tests
48 mt: 2 errors out of 102 tests
49 weak: 0 errors out of 120 tests
50 weakhash: 0 errors out of 26 tests
51 weakhash2: 0 errors out of 47 tests
52 bind-eval: 0 errors out of 72 tests
53 bind-compile: 0 errors out of 72 tests
54 conditions: 0 errors out of 98 tests
55 restarts: 0 errors out of 71 tests
56 excepsit: 0 errors out of 395 tests
57 weakptr: 0 errors out of 260 tests
Real time: 68.01543 sec.
Run time: 59.912647 sec.
Space: 1416624568 Bytes
GC: 1241, GC time: 13.156419 sec.
6
Bye.
make[2]: Leaving directory '/tmp/guix-build-clisp-2.49-92.drv-0/source/src/tests'
--8<---------------cut here---------------end--------------->8---
(From <https://ci.guix.gnu.org/build/4597797/log>.)
I reported it upstream but there seems to be relatively little activity:
https://gitlab.com/gnu-clisp/clisp/-/issues/51
Ideas on how to investigate/fix/work around? This is blocking basically
all things Common Lisp on ‘core-updates’.
Ludo’.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: CLISP test failures on ‘core-updates’
2024-06-08 20:46 CLISP test failures on ‘core-updates’ Ludovic Courtès
@ 2024-06-08 21:55 ` Guillaume Le Vaillant
2024-06-08 22:04 ` Guillaume Le Vaillant
0 siblings, 1 reply; 4+ messages in thread
From: Guillaume Le Vaillant @ 2024-06-08 21:55 UTC (permalink / raw)
To: Ludovic Courtès
Cc: cox.katherine.e+guix, me, sharlatanus, jgart, guix-devel
[-- Attachment #1: Type: text/plain, Size: 5451 bytes --]
Ludovic Courtès <ludo@gnu.org> skribis:
> Hello Lisp team! :-)
>
> The ‘clisp’ package has a few test failures on ‘core-updates’
> (x86_64-linux):
>
> --8<---------------cut here---------------start------------->8---
> finished 57 files: 6 errors out of 11,960 tests
> 1 alltest: 0 errors out of 636 tests
> 2 array: 0 errors out of 290 tests
> 3 backquot: 0 errors out of 89 tests
> 4 bin-io: 0 errors out of 15 tests
> 5 characters: 0 errors out of 221 tests
> 6 clos: 0 errors out of 496 tests
> 7 defhash: 0 errors out of 6 tests
> 8 encoding: 0 errors out of 36 tests
> 9 eval20: 0 errors out of 50 tests
> 10 ext-clisp: 1 error out of 118 tests
> 11 ffi: 0 errors out of 263 tests
> 12 floeps: 0 errors out of 20 tests
> 13 format: 0 errors out of 307 tests
> 14 genstream: 0 errors out of 14 tests
> 15 hash: 0 errors out of 48 tests
> 16 hashlong: 0 errors out of 14 tests
> 17 hashtable: 0 errors out of 10 tests
> 18 iofkts: 0 errors out of 228 tests
> 19 lambda: 0 errors out of 90 tests
> 20 lists151: 0 errors out of 201 tests
> 21 lists152: 0 errors out of 255 tests
> 22 lists153: 0 errors out of 1 test
> 23 lists154: 0 errors out of 46 tests
> 24 lists155: 0 errors out of 25 tests
> 25 lists156: 0 errors out of 20 tests
> 26 list-set: 0 errors out of 10 tests
> 27 loop: 0 errors out of 151 tests
> 28 macro8: 0 errors out of 253 tests
> 29 map: 0 errors out of 64 tests
> 30 mop: 0 errors out of 225 tests
> 31 number: 0 errors out of 3,655 tests
> 32 number2: 0 errors out of 331 tests
> 33 pack11: 0 errors out of 211 tests
> 34 path: 0 errors out of 179 tests
> 35 readtable: 0 errors out of 27 tests
> 36 setf: 0 errors out of 197 tests
> 37 socket: 0 errors out of 92 tests
> 38 steele7: 0 errors out of 86 tests
> 39 streams: 2 errors out of 388 tests
> 40 streamslong: 1 error out of 25 tests
> 41 strings: 0 errors out of 409 tests
> 42 symbol10: 0 errors out of 152 tests
> 43 symbols: 0 errors out of 6 tests
> 44 time: 0 errors out of 22 tests
> 45 tread: 0 errors out of 395 tests
> 46 type: 0 errors out of 289 tests
> 47 unportable: 0 errors out of 31 tests
> 48 mt: 2 errors out of 102 tests
> 49 weak: 0 errors out of 120 tests
> 50 weakhash: 0 errors out of 26 tests
> 51 weakhash2: 0 errors out of 47 tests
> 52 bind-eval: 0 errors out of 72 tests
> 53 bind-compile: 0 errors out of 72 tests
> 54 conditions: 0 errors out of 98 tests
> 55 restarts: 0 errors out of 71 tests
> 56 excepsit: 0 errors out of 395 tests
> 57 weakptr: 0 errors out of 260 tests
> Real time: 68.01543 sec.
> Run time: 59.912647 sec.
> Space: 1416624568 Bytes
> GC: 1241, GC time: 13.156419 sec.
> 6
> Bye.
> make[2]: Leaving directory '/tmp/guix-build-clisp-2.49-92.drv-0/source/src/tests'
> --8<---------------cut here---------------end--------------->8---
>
> (From <https://ci.guix.gnu.org/build/4597797/log>.)
>
> I reported it upstream but there seems to be relatively little activity:
>
> https://gitlab.com/gnu-clisp/clisp/-/issues/51
>
> Ideas on how to investigate/fix/work around? This is blocking basically
> all things Common Lisp on ‘core-updates’.
>
> Ludo’.
Hi.
I just tried building CLISP a few times on x86-64, and I also see a few
errors in the test report (although not exactly the same number as in
the log on the CI), but they don't make the build fail.
I think the real issue the CI got is:
--8<---------------cut here---------------start------------->8---
building of `/gnu/store/8dp91kjmlw0n6knvzpw2glsmvh9vw47r-clisp-2.49-92.drv' timed out after 3600 seconds of silence
@ build-failed /gnu/store/8dp91kjmlw0n6knvzpw2glsmvh9vw47r-clisp-2.49-92.drv - timeout
--8<---------------cut here---------------end--------------->8---
I was not able to reproduce that.
Maybe the CI just had a hiccup... I restarted the build, maybe it will
be enough.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-06-17 12:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-06-08 20:46 CLISP test failures on ‘core-updates’ Ludovic Courtès
2024-06-08 21:55 ` Guillaume Le Vaillant
2024-06-08 22:04 ` Guillaume Le Vaillant
2024-06-17 12:56 ` Ludovic Courtès
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).