You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Actions has deprecated its Ubuntu 18.04 runners, and they will be
removed by December 1, 2022. Moreover, GitHub Actions now offers Ubuntu 22.04
runners. It seems like a good time to upgrade our CI accordingly.
Somewhat annoyingly, the `haskell` Docker images that we use in our Dockerfiles
use such an old version of Debian that their version of `glibc` is incompatible
with any of the `what4-solvers` built for Ubuntu 20.04 or 22.04. As a result, I
switched them from the `haskell` Docker image to the `ubuntu` one. This
required some minor tweaks to how dependencies are installed, but nothing too
serious.
Fixes#1741. By upgrading the version of the solvers being used, this also
fixes#1744.
Copy file name to clipboardexpand all lines: s2nTests/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ This directory contains Docker configurations for running some more complex cryp
3
3
(These are the same configurations used in our GitHub Actions CI.)
4
4
5
5
## Building SAWScript
6
-
Running `make saw-script` will build SAWScript from the current working tree and place the resulting `saw` binary in `bin/`. This is useful if you develop on a system that isn't binary-compatible with Ubuntu 18.04 (e.g. macOS or NixOS).
6
+
Running `make saw-script` will build SAWScript from the current working tree and place the resulting `saw` binary in `bin/`. This is useful if you develop on a system that isn't binary-compatible with Ubuntu 22.04 (e.g. macOS or NixOS).
7
7
8
8
## Running tests
9
9
Running `make <target>` on one of the following targets will use the `saw` binary in `bin/` to run the respective proof:
0 commit comments