Re:Question about the GitLab runners at cl.net

David Cooper <[email protected]> Tue, 28 Apr 2026 19:14:23 -0400
Newsgroups gmane.lisp.common-lisp-net.devel
Message-ID <[email protected]>
------=_Part_2066171_1710557529.1777418063632
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Robert,=C2=A0




Any "insight" i would claim would be speculation.=C2=A0



Can you watch the log vs. the one you run at home in under 3 minutes? Might=
 the log reveal one or more bottlenecks in the build or test process? (this=
 is standard ASDF test suite you're talking about?)=C2=A0

=C2=A02+ minutes vs. timing out up to an hour points to something pathologi=
cal going on, our CPUs can't be _that_ much slower.=C2=A0




Dave Cooper















From: Robert Goldman <[email protected]>
To: "Discussion about the development of common-lisp.net,   the site and th=
e project."<[email protected]>
Date: Tue, 28 Apr 2026 18:02:09 -0400
Subject: Question about the GitLab runners at cl.net



I have been having troubles with the ASDF tests on GitLab.  The ASDF tests =
are timing out reliably on Clozure Common Lisp after an hour.  The same tes=
ts on a local Linux server takes only 2m30s.=20
=20
This machine has 16=C2=A0=C2=A0=C2=A0=C2=A0cores, but the ASDF tests are no=
t multi-threaded.  The processors are Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.5=
0GHz=20
=20
Those are pretty good, but by no means cutting edge.=20
=20
So I'm wondering if there's anything funny about the configuration of the G=
itLab runner.=20
=20
Thanks for any insight.=20
=20
If I can, I will mirror this repo locally and see how the runtime differs o=
n our runner.
------=_Part_2066171_1710557529.1777418063632
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>=
<meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"></h=
ead><body ><div style=3D"font-family: Verdana, Arial, Helvetica, sans-serif=
; font-size: 10pt;"><div><br></div><div>Hi Robert,&nbsp;<br><br></div><div>=
<br></div><div>Any "insight" i would claim would be speculation.&nbsp;<br><=
/div><div><br></div><div>Can you watch the log vs. the one you run at home =
in under 3 minutes? Might the log reveal one or more bottlenecks in the bui=
ld or test process? (this is standard ASDF test suite you're talking about?=
)&nbsp;<br><br>&nbsp;2+ minutes vs. timing out up to an hour points to some=
thing pathological going on, our CPUs can't be _that_ much slower.&nbsp;<br=
><br></div><div><br></div><div id=3D"Zm-_Id_-Sgn" data-sigid=3D"45069310000=
00010003" data-zbluepencil-ignore=3D"true"><div>Dave Cooper<br></div></div>=
<div><br><br><br><br></div><div class=3D"zmail_extra_hr" style=3D"border-to=
p: 1px solid rgb(204, 204, 204); height: 0px; margin-top: 10px; margin-bott=
om: 10px; line-height: 0px;"><br><br><br><br><br></div><div class=3D"zmail_=
extra" data-zbluepencil-ignore=3D"true"><div><br></div><div id=3D"Zm-_Id_-S=
gn1">From: Robert Goldman &lt;[email protected]&gt;<br>To: "Discussion ab=
out the development of common-lisp.net,   the site and the project."&lt;clo=
[email protected]&gt;<br>Date: Tue, 28 Apr 2026 18:02:09 -0400<br>Subj=
ect: Question about the GitLab runners at cl.net<br></div><div><br></div><b=
lockquote id=3D"blockquote_zmail" style=3D"margin: 0px;"><div>I have been h=
aving troubles with the ASDF tests on GitLab.  The ASDF tests are timing ou=
t reliably on Clozure Common Lisp after an hour.  The same tests on a local=
 Linux server takes only 2m30s. <br> <br>This machine has 16&nbsp;&nbsp;&nb=
sp;&nbsp;cores, but the ASDF tests are not multi-threaded.  The processors =
are Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz <br> <br>Those are pretty goo=
d, but by no means cutting edge. <br> <br>So I'm wondering if there's anyth=
ing funny about the configuration of the GitLab runner. <br> <br>Thanks for=
 any insight. <br> <br>If I can, I will mirror this repo locally and see ho=
w the runtime differs on our runner. <br></div></blockquote></div><div><br>=
</div></div><br></body></html>
------=_Part_2066171_1710557529.1777418063632--