GitHub is deprecating (and eventually removing) its macOS 10.15 runners.
See actions/virtual-environments#5583. Let's upgrade to a newer version in the
CI. This proves relatively straightforward—the only other change required is to
upgrade to a newer version of `what4-solvers`.
Previously, we would include every file in the current `cryptol` checkout in
`cryptol.msi`, which would result in horribly bloated installer files. We now
only include those files under the `dist` directory (created by
`.github/ci.sh bundle_files`), which curates only those files we want to
include in a binary distribution.
While I was in town, I modified the conventioned used in `win32/cryptol.wxs`
so that we no longer need to reference `dist`, which does not show up in
`.tar.gz`-based bindists.
Fixes#977.
This is done purely for the sake of increasing our coverage of Linux when
making releases. See #1140 for the motivation.
We won't run any of the tests et al. for this job.
The previous `what4-solvers` snapshot used Z3 4.8.10, which is known to cause
severe performance regressions with the `negshift` regression test. See #1107.
This updates to a more recent `what4-solvers` snapshot that uses Z3 4.8.14
instead, which is known to work more reliably with `negshift`.
* Disable Windows RPC tests
They seem to hang instead of failing at the moment, so until we get them
working it seems like it's better to just leave them out.
* Attempt to make "portability" build only run nightly.
This disables RPC tests on Windows. They seem to hang instead of failing at the moment, so until we get them
working it seems like it's better to just leave them out.
We will need a better solution to getting CVC4 eventually, but unbreaking the builds, even temporarily, is high priority. And the right solution for CVC4, with the recent transition to CVC5, is somewhat tricky.
Add support for TLS connections in both the rpc server
and client. Allow the client to disable certificate validation
via the `verify` keyword argument, i.e.,
`cryptol.connect(verify=False)`. The docker container
for `cryptol-remote-api` also contains a self-signed
cert for testing purposes.
Co-authored-by: Andrew Kent <andrew@galois.com>