GitLab

Staticlib for Wasmer means that the wasm has already been compiled down to machine code and is ready to run natively (IoT devices). Since we're mainly interested in how the compiler behaves with test programs, I'm removing the staticlib tests.

With documentation! 

since detailed mode is pointed to the config, we don't need to parse all the other options, just the seed. Previously, we would depend on the seed being printed out on its own line, but it could also be included as part of the command line options

Some of the configurations with wasmer are causing crashes all the time. In order to run an actual fuzzing campaign, I'm commenting out those specific tests for now

Somehow the ansible version doesn't like to see the updated repositories that we added.

(hopefully) WIP

Before, if xsmith crashed for whatever reason, there would be no output in the log to help narrow down the cause outside of the generated file. Now, the std_out and std_error of the command are captured and reported in the log.

Sadly, this doesn't eliminate the need for root, but it does make
poking around post-mortem much easier

Pending on the fixing of this issue in wasmer: https://github.com/wasmerio/wasmer/issues/2590