Problem description

The new GitHub actions CI appears to not time out (or only after an exorbitantly long time - I've seen runs beyond 16 hours at this point), and there may not be a way for contributors to stop runners once they are deployed.

Steps to reproduce

Presumably, any unit test with an infinite loop will trigger this behavior.

Behavior

Runners become unresponsive; an attempt to terminate by pushing a new/corrected version will result in the new version remaining queued.

System information

N/A

Additional context

How to specify a timeout for GitHub actions

Action to cancel current runners

Current Actions overview on Cantera/cantera

There appear to be several unresponsive runners in #892 that I am unable to terminate.