(Busted < 2.0.0-1 is horribly broken. Hell, even that is broken, too. Ideally, we should be running scm-2 (scm-1 is broken, too), but it's not on Luarocks, only in the upstream repo).

@NiLuJe

(Busted < 2.0.0-1 is horribly broken. Hell, even that is broken, too. Ideally, we should be running scm-2 (scm-1 is broken, too), but it's not on Luarocks, only in the upstream repo).

We use(d) 2.0.0-1. It works for me locally and it's always worked. Could you expand a bit on what you think the problem is?

Actually I just realized the Docker images comes with busted preinstalled and 2.0.0-0 at that. So this is both a wasted effort and possibly futile if there's a slight hiccup somewhere.

We basically need lunarmodules/busted@2dfff99 not to horribly blow up because of our use of ffi.metatype & ffi.gc.

That isn't in anything else other than scm-2, which isn't on Luarocks.

The local versions of said hackery we used to ship are too late in the pipeline to matter, AFAICT.

(Sidebar: there's one in base as ffi_wrapper, too).

We basically need lunarmodules/busted@2dfff99 not to horribly blow up because of our use of ffi.metatype & ffi.gc.

That doesn't help though.

Then it's something else ;/. A backtrace might help.

(FWIW, I'm running scm-2 here and everything passes).

(FWIW, I'm running scm-2 here and everything passes).

As I said, everything passes regardless of the version here. ;-)

It's on CircleCI that it segfaults.