clisp: build failure: failing tests

  • Done
  • quality assurance status badge
Details
3 participants
  • Christopher Howard
  • Guillaume Le Vaillant
  • zimoun
Owner
unassigned
Submitted by
Christopher Howard
Severity
normal

Debbugs page

Christopher Howard wrote 4 years ago
(name . bug-guix)(address . bug-guix@gnu.org)
dfd93fcbdbe8097ec49145dae4750acdcb8a5cdf.camel@librehacker.com
Attempting to build clisp from source results in these test failures:
```(echo *.erg | grep '*' >/dev/null) || (echo "Test failed:" ; ls -l
*erg; echo "To see which tests failed, type" ; echo " cat
"`pwd`"/*.erg" ; exit 1)Test failed:-rw-r--r-- 1 nixbld nixbld 188 Jun
30 21:15 path.erg-rw-r--r-- 1 nixbld nixbld 658 Jun 30 21:15
streams.erg-rw-r--r-- 1 nixbld nixbld 500 Jun 30 21:15
streamslong.ergTo see which tests failed, type cat /tmp/guix-build-
clisp-2.49-92.drv-0/source/src/tests/*.ergmake[2]: *** [Makefile:34:
compare] Error 1make[2]: Leaving directory '/tmp/guix-build-clisp-2.49-
92.drv-0/source/src/tests'make[1]: *** [Makefile:2216: check-tests]
Error 2make[1]: Leaving directory '/tmp/guix-build-clisp-2.49-92.drv-
0/source/src'make: *** [Makefile:28: check] Error 2
Test suite failed, dumping logs.command "make" "check" "-j" "1" failed
with status 2
```
I did a pull about one or two hours ago.
```christopher@theoden ~/Repos/guix$ neofetch --stdoutchristopher@theoden ------------------- OS: Guix System 364db4fdf664d7987693a6935b76f34258041865 x86_64 Host: OptiPlex 9020 00 Kernel: 5.12.8-gnu Uptime: 6 days, 2 hours, 44 mins Packages: 93 (guix-system), 111 (guix-user) Shell: bash 5.0.16 Resolution: 1920x1080 DE: GNOME Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: kitty CPU: Intel i5-4570 (4) @ 3.600GHz GPU: Intel HD Graphics GPU: AMD ATI Radeon HD 8490 / R5 235X OEM Memory: 4062MiB / 7869MiB```
--
Christopher Howard
Gemini capsule: gemini://gem.librehacker.com
Attachment: file
Guillaume Le Vaillant wrote 4 years ago
(name . Christopher Howard)(address . christopher@librehacker.com)(address . 49307@debbugs.gnu.org)
87czs2fp54.fsf@kitej
Christopher Howard <christopher@librehacker.com> skribis:

Toggle quote (18 lines)
> Attempting to build clisp from source results in these test failures:
> ```(echo *.erg | grep '*' >/dev/null) || (echo "Test failed:" ; ls -l
> *erg; echo "To see which tests failed, type" ; echo " cat
> "`pwd`"/*.erg" ; exit 1)Test failed:-rw-r--r-- 1 nixbld nixbld 188 Jun
> 30 21:15 path.erg-rw-r--r-- 1 nixbld nixbld 658 Jun 30 21:15
> streams.erg-rw-r--r-- 1 nixbld nixbld 500 Jun 30 21:15
> streamslong.ergTo see which tests failed, type cat /tmp/guix-build-
> clisp-2.49-92.drv-0/source/src/tests/*.ergmake[2]: *** [Makefile:34:
> compare] Error 1make[2]: Leaving directory '/tmp/guix-build-clisp-2.49-
> 92.drv-0/source/src/tests'make[1]: *** [Makefile:2216: check-tests]
> Error 2make[1]: Leaving directory '/tmp/guix-build-clisp-2.49-92.drv-
> 0/source/src'make: *** [Makefile:28: check] Error 2
> Test suite failed, dumping logs.command "make" "check" "-j" "1" failed
> with status 2
> ```
> I did a pull about one or two hours ago.
> ```christopher@theoden ~/Repos/guix$ neofetch --stdoutchristopher@theoden ------------------- OS: Guix System 364db4fdf664d7987693a6935b76f34258041865 x86_64 Host: OptiPlex 9020 00 Kernel: 5.12.8-gnu Uptime: 6 days, 2 hours, 44 mins Packages: 93 (guix-system), 111 (guix-user) Shell: bash 5.0.16 Resolution: 1920x1080 DE: GNOME Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: kitty CPU: Intel i5-4570 (4) @ 3.600GHz GPU: Intel HD Graphics GPU: AMD ATI Radeon HD 8490 / R5 235X OEM Memory: 4062MiB / 7869MiB```

It builds successfully on my machine (with Guix
at 460392d1f0d0ef5484df8834452cf94f211bf346).
Do you get this test failure every time?
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCYN1z9w8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9PagD/XZQUNjfryM7UahBDqmODz21uJE7Dm/hwiSA2
vE0bDqUBAJxtgQHmEkLce1mjnVrvrKqra9RBPcyvhLyk0robVe5K
=rGHz
-----END PGP SIGNATURE-----

Christopher Howard wrote 4 years ago
(name . Guillaume Le Vaillant)(address . glv@posteo.net)(address . 49307@debbugs.gnu.org)
05578c4bd2adfe2009a44689a932b11330feda0a.camel@librehacker.com
Hi, yes, I am able to reproduce the error, even when I switch to your
guix commit (using time-machine).
zimoun wrote 4 years ago
(address . 49307@debbugs.gnu.org)
86a6n3alqv.fsf@gmail.com
Hi Chris,

On Thu, 01 Jul 2021 at 09:37, Christopher Howard <christopher@librehacker.com> wrote:
Toggle quote (3 lines)
> Hi, yes, I am able to reproduce the error, even when I switch to your
> guix commit (using time-machine).

As Guillaume, CLISP builds successfully for me too.

Could this bug related to your message [1]:

Something is certainly corrupted somewhere, but I can't figure
out where, or what it is exactly that I need to repair or delete
or whatever.
?

1:

All the best,
simon
zimoun wrote 4 years ago
(name . Christopher Howard)(address . christopher@librehacker.com)
8635sipqhp.fsf@gmail.com
Hi Christopher,

On Sat, 03 Jul 2021 at 09:40, zimoun <zimon.toutoune@gmail.com> wrote:
Toggle quote (18 lines)
> On Thu, 01 Jul 2021 at 09:37, Christopher Howard <christopher@librehacker.com>
> wrote:
>> Hi, yes, I am able to reproduce the error, even when I switch to your
>> guix commit (using time-machine).
>
> As Guillaume, CLISP builds successfully for me too.
>
> Could this bug related to your message [1]:
>
> Something is certainly corrupted somewhere, but I can't figure
> out where, or what it is exactly that I need to repair or delete
> or whatever.
>
> ?
>
> 1:
> <https://yhetil.org/guix/e0e21927198fb55f82784c0f3ad661d82104c80e.camel@librehacker.com>

Is it still an issue for you?

All the best,
simon
Christopher Howard wrote 4 years ago
(name . zimoun)(address . zimon.toutoune@gmail.com)
3ce371520d41479df39a993258f2bdce69559634.camel@librehacker.com
Hello. The clisp build failure occured on my work computer, whereas the file corruption occurred on my home computer. Incidentally, I gave up home off solving the corruption issue and has to wipe and
reinstall guix on that system. I will try to rebuild the clisp package now on both systems.

--
Christopher Howard
my gemini capsule: gemini://gem.librehacker.com


On Tue, 2021-07-13 at 10:28 +0200, zimoun wrote:
Toggle quote (25 lines)
> Hi Christopher,
>
> On Sat, 03 Jul 2021 at 09:40, zimoun <zimon.toutoune@gmail.com> wrote:
> > On Thu, 01 Jul 2021 at 09:37, Christopher Howard <christopher@librehacker.com>
> > wrote:
> > > Hi, yes, I am able to reproduce the error, even when I switch to your
> > > guix commit (using time-machine).
> >
> > As Guillaume, CLISP builds successfully for me too.
> >
> > Could this bug related to your message [1]:
> >
> > Something is certainly corrupted somewhere, but I can't figure
> > out where, or what it is exactly that I need to repair or delete
> > or whatever.
> >
> > ?
> >
> > 1:
> > <https://yhetil.org/guix/e0e21927198fb55f82784c0f3ad661d82104c80e.camel@librehacker.com>
>
> Is it still an issue for you?
>
> All the best,
> simon
Christopher Howard wrote 4 years ago
(name . zimoun)(address . zimon.toutoune@gmail.com)
7028ff9a946447430245a058bcd76da08f4ef4a1.camel@librehacker.com
Hi, I'm not having trouble building clisp now from either my home nor
my work computer.

-----Original Message-----
From: Christopher Howard <christopher@librehacker.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guillaume Le Vaillant <glv@posteo.net>, 49307@debbugs.gnu.org
Subject: Re: bug#49307: clisp: build failure: failing tests
Date: Tue, 13 Jul 2021 06:13:41 -0800

Hello. The clisp build failure occured on my work computer, whereas the
file corruption occurred on my home computer. Incidentally, I gave up
home off solving the corruption issue and has to wipe and
reinstall guix on that system. I will try to rebuild the clisp package
now on both systems.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 49307@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 49307
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help