CI for pygwinc
Now that we have a CLI and test suite, we should create a pygwinc CI that takes advantage of them.
Maintenance will be performed on git.ligo.org, containers.ligo.org, and docs.ligo.org on Tuesday 22 April 2025 starting at approximately 9am PDT. It is expected to take around 30 minutes and there will be several periods of downtime throughout the maintenance. Please address any comments, concerns, or questions to the helpdesk. This maintenance will be upgrading the GitLab database in order to be ready for the migration.
Now that we have a CLI and test suite, we should create a pygwinc CI that takes advantage of them.
mentioned in commit e959ada0
An initial CI is now working that just renders a figure for the README.
@jameson.rollins Any news on accessing matlab within the git.ligo.org CI runners?
Maybe an easier approach for gitlab is to have a .mat file of cached results from matgwinc, against which pygwinc can be tested.
We have a basic CI now that runs the comparison tests, although the CI is currently not failing on fail of the comparison because we have some outstanding differences to resolve.
closed