Context
We are working on a complex compiler architecture where small changes can break other parts of the code while fixing the part we are currently working on. Therefore, we need a check target that performs a global verification of the HybroGen build and runs unit tests to ensure that local changes have not introduced any bugs.
Goal
The goal is to:
- Create a target called
check that the user can run after buildAll to ensure their HybroGen build is valid
- Verify that the database is not empty and that all architectures are properly registered
- Run regression tests to ensure that all architectures are correctly built
- (Optional) Run demos to confirm that the user is able to reproduce results as shown in the paper
Note
I believe that every well-maintained public GitHub repository provides both build and check targets. Adding this feature would be a strong improvement, and it should be maintained over time by integrating new unit tests and demos as they are developed.
This can look like CI purposes, but CI is slightly different: the check target verifies that everything works on the user's local machine, whereas CI verifies that it works on a remote Lambda environment running an Ubuntu target version.
Context
We are working on a complex compiler architecture where small changes can break other parts of the code while fixing the part we are currently working on. Therefore, we need a
checktarget that performs a global verification of the HybroGen build and runs unit tests to ensure that local changes have not introduced any bugs.Goal
The goal is to:
checkthat the user can run afterbuildAllto ensure their HybroGen build is validNote
I believe that every well-maintained public GitHub repository provides both
buildandchecktargets. Adding this feature would be a strong improvement, and it should be maintained over time by integrating new unit tests and demos as they are developed.This can look like CI purposes, but CI is slightly different: the
checktarget verifies that everything works on the user's local machine, whereas CI verifies that it works on a remote Lambda environment running an Ubuntu target version.