Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CI: Upgrade the Ubuntu versions used for binary distributions #1741

Closed
RyanGlScott opened this issue Sep 19, 2022 · 0 comments · Fixed by #1746
Closed

CI: Upgrade the Ubuntu versions used for binary distributions #1741

RyanGlScott opened this issue Sep 19, 2022 · 0 comments · Fixed by #1746
Labels
tooling: CI Issues involving CI/CD scripts or processes

Comments

@RyanGlScott
Copy link
Contributor

Currently, the CI only builds a Linux binary distribution for Ubuntu 18.04. This is troublesome for a couple of reasons:

  1. 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.
  2. In order to increase our Linux coverage, it would be wise to have binary distributions for both Ubuntu 22.04 and 20.04. Ideally, most of our testing would be done on 22.04, but we can reserve one Linux CI job for 20.04, which would also produce the binary artifact.

I have done this previously for Cryptol (GaloisInc/cryptol#1403) and for Crux (GaloisInc/crucible#1026), so now we should do the same thing for SAW.
@RyanGlScott RyanGlScott added the tooling: CI Issues involving CI/CD scripts or processes label Sep 19, 2022
@RyanGlScott RyanGlScott mentioned this issue Sep 30, 2022
Closed
RyanGlScott added a commit that referenced this issue Oct 3, 2022
@RyanGlScott
CI: Use Ubuntu 22.04, drop 18.04
de3e7cb 
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.
@RyanGlScott RyanGlScott mentioned this issue Oct 3, 2022
Merged
RyanGlScott added a commit that referenced this issue Oct 10, 2022
@RyanGlScott
CI: Use Ubuntu 22.04, drop 18.04
394cf18 
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.
RyanGlScott added a commit that referenced this issue Oct 10, 2022
@RyanGlScott
CI: Use Ubuntu 22.04, drop 18.04
cf30702 
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.
@mergify mergify bot closed this as completed in #1746 Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tooling: CI Issues involving CI/CD scripts or processes
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

CI: Use Ubuntu 22.04, drop 18.04 GaloisInc/saw-script
1 participant
@RyanGlScott