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.

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

Add check-docstrings to CI #128

Open
2 tasks
marsella opened this issue Aug 29, 2024 · 1 comment
Open
2 tasks

Add check-docstrings to CI #128

marsella opened this issue Aug 29, 2024 · 1 comment
Labels
CI enhancement New feature or request

Comments

@marsella
Copy link
Contributor

marsella commented Aug 29, 2024

I'm starting to make changes to interfaces that cascade down to multiple files and I'm less confident that I'm checking all the the properties in all the dependencies still work. I'd like to add a CI run that addresses this concern without being outrageously slow.

My ideal version would

  1. Identify all the Cryptol files that changed
  2. Recursively identify all files that depend on each changed file
  3. Load and run :check-docstrings on each file in the set (1 + 2). In parallel, ideally.

I'm not sure what the best way to do 2 is. We have pretty well specified module path names so it might be as straightforward as grepping the whole repo for each file name. There are also some built-in tools that identify dependencies (:module-deps) for a given file, but we'd have to do that "in reverse" (that is, we want the files that depend on X, not the dependencies of X). There might be another way to use haskell / cryptol internals to get the dependency tree.

Related: #56.

  • Choose an approach for this bit of CI
  • Write all the scripts + yml files
@mccleeary-galois mccleeary-galois added enhancement New feature or request CI labels Aug 29, 2024
@mccleeary-galois
Copy link
Contributor

We also need to ensure that we are targeting the solvers that we ship with https://github.com/GaloisInc/what4-solvers/releases/tag/snapshot-20240212 for now. More discussion across ecosystem as a whole needs to happen for solver versions in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants