Add py3.11 to test matrix

[kandersolar]

No description provided.

[AdamRJensen]

Would it make sense to also have the tests run on a cron schedule, e.g., once a week or month? I imagine that we won't have many PRs in the future, and thus we would detect issues like #39 with a significant delay.

[kandersolar]

Would it make sense to also have the tests run on a cron schedule, e.g., once a week or month?

I think running them once a week or so is a good idea. What's a good way to make test failures noisy enough to make us notice? I think it's possible to have a CI job open github issues. Maybe just emailing us is enough.

[AdamRJensen]

I think running them once a week or so is a good idea. What's a good way to make test failures noisy enough to make us notice? I think it's possible to have a CI job open github issues. Maybe just emailing us is enough.

How about adding a cron schedule to the GitHub Actions? The below example would run at 00:00 every Sunday.

on:
  schedule:
    - cron: '0 0 * * 0'

In case of failure, wouldn't that email us? I think that should be sufficient - no need for a complicated workflow that creates an issue.

[kandersolar]

In case of failure, wouldn't that email us?

I don't receive email notifications for CI failures in any other job. Probably it's possible to get them somehow. I would only want to enable them if they can be enabled per repo or even per workflow though :)

[AdamRJensen]

I don't receive email notifications for CI failures in any other job. Probably it's possible to get them somehow. I would only want to enable them if they can be enabled per repo or even per workflow though :)

Good point - let's tackle this in another issue/PR since it's not time-sensitive and does not require a new release.

[AdamRJensen]

Thanks, @kanderso-nrel - you're a champ!