-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some systems failed to build for Quicklisp dist #6
Comments
This should be fixed with the latest commit 31e2e70 and tag. |
|
I have addressed this in 31f298d and have updated the latest tag to point to the same. |
Is the commit information this build is using visible anywhere? I'm unable to reproduce it locally using the latest commit/tag; plus the CI also passes. |
This is when building 31f298d
…On Wed, Jun 21, 2023 at 3:10 AM Shubhamkar Ayare ***@***.***> wrote:
Is the commit information this build
<http://report.quicklisp.org/2023-06-20/failure-report/numericals.html#numericals.common>
is using visible anywhere? I'm unable to reproduce it locally using the
latest commit/tag; plus the CI also passes.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPNLK45YVDNMCMTPH6ZRDXMKM4RANCNFSM6AAAAAAZHXASYA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
And, please confirm, we need to ensure that the system is loadable with I can confirm that the issue exists prior to 31f298d - it exists for 31e2e70 - but is resolved for 31f298d itself. I had also force pushed the tag to make it point to 31f298d instead of 31e2e70 earlier, in case that becomes an issue. |
Building with SBCL 2.3.3.83-562a1a329 / ASDF 3.3.5 for quicklisp dist creation.
Trying to build commit id c8dd3ab
dense-numericals fails to build with the following error:
dense-numericals/magicl fails to build with the following error:
numericals/benchmarks fails to build with the following error:
Full log here
The text was updated successfully, but these errors were encountered: