GitLab

By embedding part of lunit into a binary and bending the startup
machinery to our needs. The original lunit launcher couldn't be used,
because we include bunch of functions and modules directly into our
interpreter (either from auto-loaded lua files or from C code).

Fill the result of loaded chunk into the package.loaded, so future
require(name) works on such preloaded module. Make it work with module()
in the code as well.

Also, fix segfault when passing NULL as results parameter to
interpreter_call.

• Add the logging functions to lua as well as C code.
• Add few tests for the lua logging (to check the magic with generating
  functions).
• Turn off logging in make check (they still may be run manually to get
  all the logging).

And use them through the code. Also use provided ASSERT macro instead of
assert(), to ensure it is not compiled out and the output is logged to
all future locations the logs would go.

• Replace the event_active call with separate event with 0 timeout. The
  original didn't seem to work.
• Run multiple children in parallel to ensure the event loop can handle
  that as well.
• Limit number of valgrind iterations (just to make it run faster).

Some tests failed with timeout. Make it larger as an attempt to verify
if it is because of long running time or lockup.

The event loop & ability to wait for PIDs. Not used or tested yet.

Provide an error handler. Also, store the auto-loaded "modules" to
global space.

Implement the interpreter_collect_results functions; pass the tests.

Pass parameters given to interpreter_call to the actual lua function.

Some more progress with the tests O:-).

But without the parameters. Tests still don't pass, but some get
further.

Provide declarations of functions to call lua functions from C
conveniently. Also, make some tests about them. But as the
implementation is just a dummy, they don't pass.

This way we may use the loaded code in tests.

These'll later work as libraries of functions to be called at convenient
time.

• Remove some unnecessary cruft.
• Prefix the test binaries with ctest-, so they don't clash with
  anything.
• Make it work with more than one test binary.

Create and destroy an interpreter in the opkg-trans program.

This is not nuci configuration server (copy-pasted from there).

At least in the only scenario where it can run successfully now ‒
requesting help.

Be able to terminate correctly, be able to print help. Inform about the
other operations not being implemented yet.

• Provide more errors
• Run the checks in non-fork mode to avoid some leaks
• Generate error exit code if anything is found