Wasmtime: remaps for coverage

[catenacyber]

cc @alexcrichton cf #5366 (comment)

This should fix wasmtime coverage build

[alexcrichton]

I always find bash a bit, uh, esoteric to read...

In any case though looks good to me, thanks!

[alexcrichton]

Could this have a comment for the purpose of what's happening? (basically just ensuring that absolute paths are used everywhere in debuginfo and such)

[alexcrichton]

Thanks for your help here!

[catenacyber]

@inferno-chromium could we merge this ?

[inferno-chromium]

@inferno-chromium could we merge this ?

Can you check CI failures, are they related to this change, can you maybe push again to see if they still happen. if not, leave a comment and we can merge.

[catenacyber]

CI is happier except for coverage failure which seems unrelated
LLVM ERROR: IO failure on output stream: No space left on device

[alexcrichton]

Thanks again for this @catenacyber, we got our first successful build today as a result.

@inferno-chromium if I go to https://oss-fuzz.com/ and click "total coverage" it links me to https://oss-fuzz.com/coverage-report/job/libfuzzer_asan_wasmtime/latest which gives me " Failed to get coverage report. (alex@alexcrichton.com) ". Is that something that needs to be configured on y'all's end? Or should I just wait a day or so for things to propagate?

[catenacyber]

There is one available here
https://storage.googleapis.com/oss-fuzz-coverage/wasmtime/reports/20210322/linux/report.html

[alexcrichton]

Oh wow, thanks! How did you end up finding the link to that?

[catenacyber]

Just clicked a link to one of my projects and replaced the name ;-)
I guess you can wait a day or two for thing to propagate...

[catenacyber]

And now your link https://oss-fuzz.com/coverage-report/job/libfuzzer_asan_wasmtime/latest works (and redirects to mine)