Stream: git-wasmtime

Topic: wasmtime / Issue #2384 Fix WasmTy/WasmRet on big-endian h...


view this post on Zulip Wasmtime GitHub notifications bot (Nov 09 2020 at 16:42):

uweigand commented on Issue #2384:

Once we have the IBM Z back-end support completed and merged, I agree it would make sense to try and add CI. Not sure if this will be possible with the current github CI, but e.g. Travis-CI offers support for adding IBM Z builders ...

view this post on Zulip Wasmtime GitHub notifications bot (Nov 09 2020 at 16:46):

bjorn3 commented on Issue #2384:

Travis-CI recently severely limited their free opensource offerings: https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

I think it may be better to use qemu on GHA.

view this post on Zulip Wasmtime GitHub notifications bot (Nov 09 2020 at 17:01):

uweigand commented on Issue #2384:

Huh, that's unfortunate. I'm not sure if qemu works sufficiently well at the moment, but I guess we can try.

Another option could be that we make available a IBM Z guest in our community cloud. However, this would mean we'd have to run whatever build agent we need ourselves on that machine. Not sure how to best integrate this into github automation ...

view this post on Zulip Wasmtime GitHub notifications bot (Nov 09 2020 at 17:09):

github-actions[bot] commented on Issue #2384:

Subscribe to Label Action

cc @peterhuene

<details>
This issue or pull request has been labeled: "wasmtime:api"

Thus the following users have been cc'd because of the following labels:

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

view this post on Zulip Wasmtime GitHub notifications bot (Nov 09 2020 at 17:14):

alexcrichton commented on Issue #2384:

Ok no worries! This seems fine to merge in the meantime. We can always figure out CI at a later date.


Last updated: Nov 22 2024 at 16:03 UTC