CI tests for jupyter notebooks are only run with the beta-master action, and only one runner within that action (ubuntu-latest, python 3.13, cython). These tests take 45 minutes on their own, to say nothing about the ~10 minutes of unit tests before we get to notebook tests.
At the very least we should have a runner within this action that immediately builds pyGSTi and runs these tests -- no waiting for unittests to pass. We could also consider creating infrastructure to have multiple runners which handle different notebook tests in an embarassingly parallel way.
The beta-master action takes about 19 minutes (at time of filing this issue) if not for these notebook tests. So the natural goal would be to split up notebook work so the whole thing takes about 20 minutes.
CI tests for jupyter notebooks are only run with the beta-master action, and only one runner within that action (ubuntu-latest, python 3.13, cython). These tests take 45 minutes on their own, to say nothing about the ~10 minutes of unit tests before we get to notebook tests.
At the very least we should have a runner within this action that immediately builds pyGSTi and runs these tests -- no waiting for unittests to pass. We could also consider creating infrastructure to have multiple runners which handle different notebook tests in an embarassingly parallel way.
The beta-master action takes about 19 minutes (at time of filing this issue) if not for these notebook tests. So the natural goal would be to split up notebook work so the whole thing takes about 20 minutes.