Fuzzing components with wasm-smith needs to be updated

[alexcrichton]

I'm disabling the tests in #966 since the preexisting support for fuzzing components with wasm-smith is outdated enough that I ended up not trying to update it. This may be as easy as "implement recent component model changes" and may also range up to "oh dear much of this needs to be rewritten". In any case I'm writing this down to record on some ignored tests.

[0xalpharush]

How would you propose generating components that conform to a given WIT? I am thinking of using wasm-smith to generate modules with the available imports/necessary exports and then embedding the component info (wasm-tools component embed sample.wit test.wasm -o output.wasm).

[alexcrichton]

One option is to use wasm-tools component embed --dummy sample.wit and that gives you a core wasm module to "fill out". That's unlikely to be too too useful though because although you can generate the core wasm signatures it's pretty unlikely that you'll generate a module that happens to use the correct canonical ABI, so almost all modules are likely to fail/trap when actually receiving or giving an argument.