-
Notifications
You must be signed in to change notification settings - Fork 119
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
Use prebuilt solver binaries from what4-solvers #1284
Conversation
0baf819
to
c537017
Compare
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.
Looks good!
We're using GHC 8.6.5 for tests
They’re stalling for unknown reasons, and aren’t as critical as the others. Running the Linux tests is the most critical.
case "$RUNNER_OS" in | ||
Linux) ldd $1 || true ;; | ||
macOS) otool -L $1 || true ;; | ||
Windows) ldd $1 || 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.
What's the intent of the || true
for these? It will always allow these to succeed, so is this just for getting logging output to show which binary is running and the validity of the available shared libs?
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.
At least ldd
(and maybe otool
?) return non-zero for statically-linked executables, and some of the executables we generate are expected to be statically linked. And, ultimately, yeah, the purpose of this is to have extra log output to help with debugging.
No description provided.