
Would anyone object to adding GitHub Actions CI to the RackUnit repo? The current travis CI setup for it seems to have been busted for a while now.

I never committed anything there and don’t even know who’s the responsible for that one. But it sounds like a good idea to move things to Actions.

according to https://github.com/racket/racket/wiki/Release-repo-managers the responsible for the repo is @ryanc

@notjack sounds like a good idea. I think just opening a PR is the right way forward.

The racket core tests long-predate rackunit. And they don’t really want to depend on them (or on anything). I think trying to change that test framework isn’t really worth it.

@samth is that test framework documented somewhere?

No. I also would strongly recommend not using it for anything else. But having internal docs for it would be nice.