CI job for lisp-team branch

CI job for lisp-team branch

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 153 bytes --]

Hi.
I created a lisp-team branch to work one some updates for clisp and
sbcl. Could someone with admin access to the CI things add a job for it?
Thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

Re: CI job for lisp-team branch

[宋文武]

Guillaume Le Vaillant <glv@posteo.net> writes:

> Hi.
> I created a lisp-team branch to work one some updates for clisp and
> sbcl. Could someone with admin access to the CI things add a job for it?
> Thanks.

Hello, Curiass CI job created.

Thanks.

Re: CI job for lisp-team branch

[Maxim Cournoyer]

Hi Guillaume,

Guillaume Le Vaillant <glv@posteo.net> writes:

> Hi.
> I created a lisp-team branch to work one some updates for clisp and
> sbcl. Could someone with admin access to the CI things add a job for it?
> Thanks.

I've also created a TLS client certificate and emailed it to you
(encrypted) so that you can manage your branch yourself via the Cuirass
web interface, restart failing builds (which are sometimes spurious
failures due to not yet resolved CI/infrastructure problems such as
#54447).

Cheers!

-- 
Thanks,
Maxim

Re: CI job for lisp-team branch

[Guillaume Le Vaillant]

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Hi Guillaume,
>
> I've also created a TLS client certificate and emailed it to you
> (encrypted) so that you can manage your branch yourself via the Cuirass
> web interface, restart failing builds (which are sometimes spurious
> failures due to not yet resolved CI/infrastructure problems such as
> #54447).
>
> Cheers!

Thanks.

Re: CI job for lisp-team branch

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

On Mon, Sep 04, 2023 at 09:27:44AM +0000, Guillaume Le Vaillant wrote:
> Hi.
> I created a lisp-team branch to work one some updates for clisp and
> sbcl. Could someone with admin access to the CI things add a job for it?
> Thanks.

I commented on IRC but figured I should post to the mailing list.

I tested sbcl@2.3.8 on riscv64-linux and the build failed in the contrib
section. I see the patch was removed, presumably because it was included
in the upstream release. When I finish my current build target(s) I'll
see what needs to be done there.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: CI job for lisp-team branch

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote:
> On Mon, Sep 04, 2023 at 09:27:44AM +0000, Guillaume Le Vaillant wrote:
> > Hi.
> > I created a lisp-team branch to work one some updates for clisp and
> > sbcl. Could someone with admin access to the CI things add a job for it?
> > Thanks.
> 
> I commented on IRC but figured I should post to the mailing list.
> 
> I tested sbcl@2.3.8 on riscv64-linux and the build failed in the contrib
> section. I see the patch was removed, presumably because it was included
> in the upstream release. When I finish my current build target(s) I'll
> see what needs to be done there.

Re-adding the patch failed hard when applying the patch. I tested
downgrading sbcl to 2.3.7 and that built everything without any trouble
on riscv64-linux.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: CI job for lisp-team branch

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote:
>> 
>> I commented on IRC but figured I should post to the mailing list.
>> 
>> I tested sbcl@2.3.8 on riscv64-linux and the build failed in the contrib
>> section. I see the patch was removed, presumably because it was included
>> in the upstream release. When I finish my current build target(s) I'll
>> see what needs to be done there.
>
> Re-adding the patch failed hard when applying the patch. I tested
> downgrading sbcl to 2.3.7 and that built everything without any trouble
> on riscv64-linux.

The patch was a backport from upstream (commit
8704f528f227f587d0e06dfd2f807aeca7a69a71), so it is already in the
sources for sbcl 2.3.8.

What error do you get when building on riscv64? Maybe we could report it
upstream as I have not seen anything about riscv64 fixes in the commit
history of sbcl since version 2.3.8.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

Re: CI job for lisp-team branch

[Efraim Flashner]

[-- Attachment #1.1: Type: text/plain, Size: 3300 bytes --]

On Thu, Sep 07, 2023 at 12:31:39PM +0000, Guillaume Le Vaillant wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
> 
> > On Wed, Sep 06, 2023 at 03:47:01PM +0300, Efraim Flashner wrote:
> >> 
> >> I commented on IRC but figured I should post to the mailing list.
> >> 
> >> I tested sbcl@2.3.8 on riscv64-linux and the build failed in the contrib
> >> section. I see the patch was removed, presumably because it was included
> >> in the upstream release. When I finish my current build target(s) I'll
> >> see what needs to be done there.
> >
> > Re-adding the patch failed hard when applying the patch. I tested
> > downgrading sbcl to 2.3.7 and that built everything without any trouble
> > on riscv64-linux.
> 
> The patch was a backport from upstream (commit
> 8704f528f227f587d0e06dfd2f807aeca7a69a71), so it is already in the
> sources for sbcl 2.3.8.
> 
> What error do you get when building on riscv64? Maybe we could report it
> upstream as I have not seen anything about riscv64 fixes in the commit
> history of sbcl since version 2.3.8.

//entering make-target-contrib.sh
make: Entering directory '/tmp/guix-build-sbcl-2.3.8.drv-0/sbcl-2.3.8/contrib'
make: *** No rule to make target 'sb-posix.fasl', needed by 'all'.
make: *** No rule to make target 'sb-bsd-sockets.fasl', needed by 'all'.
make: *** No rule to make target 'sb-introspect.fasl', needed by 'all'.
make: *** No rule to make target 'sb-cltl2.fasl', needed by 'all'.
make: *** No rule to make target 'sb-aclrepl.fasl', needed by 'all'.
make: *** No rule to make target 'sb-sprof.fasl', needed by 'all'.
make: *** No rule to make target 'sb-capstone.fasl', needed by 'all'.
make: *** No rule to make target 'sb-rotate-byte.fasl', needed by 'sb-md5.fasl'.
make: *** No rule to make target 'sb-executable.fasl', needed by 'all'.
make: *** No rule to make target 'sb-gmp.fasl', needed by 'all'.
make: *** No rule to make target 'sb-concurrency.fasl', needed by 'sb-queue.fasl'.
make: *** No rule to make target 'sb-rt.fasl', needed by 'all'.
make: *** No rule to make target 'asdf.fasl', needed by 'sb-grovel.fasl'.
make: Target 'all' not remade because of errors.
make: Leaving directory '/tmp/guix-build-sbcl-2.3.8.drv-0/sbcl-2.3.8/contrib'

real    0m0.046s
user    0m0.033s
sys     0m0.014s
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "sh" arguments: ("make.sh" "clisp" "--prefix=/gnu/store/yz18dz67jmy2vmvilxm1pbfdw8g1yky2-sbcl-2.3.8" "--dynamic-space-size=3072" "--with-sb-core-compression" "--with-sb-xref-for-internals" "--without-sb-simd") exit-status: 2 term-signal: #f stop-signal: #f>
phase `build' failed after 11808.1 seconds
command "sh" "make.sh" "clisp" "--prefix=/gnu/store/yz18dz67jmy2vmvilxm1pbfdw8g1yky2-sbcl-2.3.8" "--dynamic-space-size=3072" "--with-sb-core-compression" "--with-sb-xref-for-internals" "--without-sb-simd" failed with status 2


That's why I tried to reapply the patch, when I saw that I figured the
patch was still needed. I've attached a compressed log incase for
posterity.


-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #1.2: sbcl-2.3.8-riscv64.log.gz --]
[-- Type: application/x-gunzip, Size: 50172 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: CI job for lisp-team branch

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 127 bytes --]

I reported the issue upstream at
<https://bugs.launchpad.net/sbcl/+bug/2034713> with your log file.
Let's see what they say...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

Re: CI job for lisp-team branch

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]

Guillaume Le Vaillant <glv@posteo.net> skribis:

> I reported the issue upstream at
> <https://bugs.launchpad.net/sbcl/+bug/2034713> with your log file.
> Let's see what they say...

I downgraded sbcl to 2.3.7 on the lisp-team branch for now.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]