Conversation
Thanks very much @enjhnsn2 for all the work here! |
The CircleCI jobs on Linux are failing with the exceedingly cryptic error from
I'm looking into this a bit -- initially at least I notice that it's an old version (v0.6.1 vs latest v0.8.0) of the crate... |
Updating to latest I'm also unable to reproduce the error locally on Linux. Additionally it seems unlikely to be an issue with external environment of some sort (e.g. download at some URL became new version silently or somesuch) as another PR (#683) just passed CI and merged yesterday. @enjhnsn2 or @pchickey any other ideas? |
That error looks like the cmake on the builder isnt new enough. I have no idea why we didn't encounter the same error in 683, though. |
@enjhnsn2 I got a clean CI build on CircleCI with one more commit to update the Docker image to Ubuntu 20.04.... could you pull in the commit from this run? link (I think that CircleCI keys CI status on commit hash, so if you push exactly my commit to this PR's branch, it should get a green check automatically) |
I updated with the Docker image commit and it does seem to have triggered CircleCI 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the patience with CI! Looks good to merge now.
This updates lucet to use the most up-to-date version of VeriWasm that runs clean on lucet's fuzzer.