-
Notifications
You must be signed in to change notification settings - Fork 153
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
Fix docs build release job #4464
Conversation
RUN if [ "${INSTALL_BACKEND_DEBS}" = "true" ]; then \ | ||
apt-get -y install /llvm-backend.deb; \ | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should clean this up a bit (in a different PR): the LLVM_BACKEND_DEB_PATH
is required, even if INSTALL_BACKEND_DEBS
is not true
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, it's a slightly awkward design as it stands - will aim to clean up in a following PR per your comment below
/llvm-backend.deb \ | ||
/kframework.deb \ | ||
&& apt-get -y clean | ||
/kframework.deb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So IIUC this Docker file is used with two kinds of kframework.deb
: one that contains the LLVM backend and one that doesn't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep! We should clean that up
This PR fixes a bug that's been breaking the Pyk documentation release jobs; the issue was that we were trying to install the standalone LLVM backend
.deb
package on top of an existing K installation that already contains the LLVM backend.The fix is to add a flag to the K Docker reusable action that allows the backend installation step to be skipped. You can see a successful run of the fixed workflow here: https://github.com/runtimeverification/k/actions/runs/9604052282/job/26489371015?pr=4464