Stream: git-wasmtime

Topic: wasmtime / PR #1811 Fix build warnings (errors on CI) due...


view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 16:35):

cfallin opened PR #1811 from fix-warning to master:

Should fix recent build failures on CI.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 16:36):

bnjbvr submitted PR Review.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 16:38):

fitzgen submitted PR Review.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 16:48):

cfallin updated PR #1811 from fix-warning to master:

Should fix recent build failures on CI.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:04):

cfallin updated PR #1811 from fix-warning to master:

Should fix recent build failures on CI.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:10):

yurydelendik updated PR #1811 from fix-warning to master:

Should fix recent build failures on CI.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:20):

alexcrichton submitted PR Review.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:20):

alexcrichton created PR Review Comment:

Instead of checking in an = dependency could we leave the lock file as what's a known good version to test against? That would basically just involve dropping this from the diff. I can look into what's going on with the most recent version of backtrace soon too hopefully.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:25):

yurydelendik submitted PR Review.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:25):

yurydelendik created PR Review Comment:

yep, I used version "0.3.46" from Cargo.lock

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:27):

cfallin updated PR #1811 from fix-warning to master:

Should fix recent build failures on CI.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:27):

cfallin submitted PR Review.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:27):

cfallin created PR Review Comment:

Sure, just amended the commit to remove that.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 19:47):

cfallin updated PR #1811 from fix-warning to master:

Should fix recent build failures on CI.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (Jun 03 2020 at 20:26):

cfallin merged PR #1811.


Last updated: Nov 22 2024 at 16:03 UTC