Bring README up to date, bring CI back to old glory #145
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fhackett
force-pushed
the
fhackett-readme-and-ci
branch
from
3ffccbf
to
0a91cd9
Compare
fhackett
force-pushed
the
fhackett-readme-and-ci
branch
from
cbd5d13
to
cfb2716
Compare
|
An interesting side-effect of re-enabling the CI matrix: now the fuzz tests get to run >20x in parallel! This PR now includes misc. bugfixes for some discovered errors. |
… as part of `sbt test`
…ect a more modern API
shayanh
reviewed
Jul 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a first step in addressing issue #138 , it's fairly simple to bring the README up to date.
Many small details about how to build, run, etc are changed. Very out-of-date info is purged, and notes are made that the manual still needs updating (work in progress...).
While doing so, I realised the old README referred to a version matrix CI used to use, so I re-implemented that in the Github CI action with what I believe are currently reasonable versions. Now, that part of the README will be correct again.