Update wasmtime to the latest master.#1437
Conversation
|
r? @gnzlbg (rust_highfive has picked a reviewer for you, use r? to override) |
|
@bors: r+ |
|
📌 Commit 0ac8cef has been approved by |
Update wasmtime to the latest master. The previous wasmtime revision is broken because one of its dependencies, `memoffset` 0.3, was yanked, which appears to make it unavailable. This was fixed by downgrading to `memoffset` 0.2.
|
💔 Test failed - checks-cirrus-freebsd-12 |
|
I should mention; this PR fixes #1424. |
|
The Travis failure here looks like the same failure happening on master. |
|
Sorry that it took so long, it was unclear what was causing the master failure and it turned out to be the LLVM 9 upgrade... fun times... @bors: r+ |
|
📌 Commit e21be8c has been approved by |
Update wasmtime to the latest master. The previous wasmtime revision is broken because one of its dependencies, `memoffset` 0.3, was yanked, which appears to make it unavailable. This was fixed by downgrading to `memoffset` 0.2.
|
💔 Test failed - checks-travis |
|
@bors: retry
|
Update wasmtime to the latest master. The previous wasmtime revision is broken because one of its dependencies, `memoffset` 0.3, was yanked, which appears to make it unavailable. This was fixed by downgrading to `memoffset` 0.2.
|
☀️ Test successful - checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-travis, status-appveyor |
|
@sunfishcode the wasi build job is still failing on master (notice that it is allowed to fail). Would you mind taking a look? |
|
Looks like a compiler problem compiling the new linux_termios test for wasm. I'll investigate further when I get a chance. |
4 participants
The previous wasmtime revision is broken because one of its dependencies,
memoffset0.3, was yanked, which appears to make it unavailable. This was fixed by downgrading tomemoffset0.2.