Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set --pid=host in rb-sys-dock #487

Merged
merged 1 commit into from
Jan 14, 2025
Merged

Conversation

jbourassa
Copy link
Contributor

@jbourassa jbourassa commented Jan 13, 2025

The cross-gem action for wasmtime-rb gets killed by something, and I can't quite find out why (see bytecodealliance/wasmtime-rb#418 (comment)). But it looks like setting --pid=host fixes it, soo... why not?

The cross-gem action for wasmtime-rb succeeded (well, mostly -- the failure is unrelated) with that patch applied: https://github.com/jbourassa/wasmtime-rb/actions/runs/12754208869/

Locally, oxi-test built successfully with Docker on my M2 mac:

~/src/rb-sys/gem/exe/rb-sys-dock --platform x86_64-linux --directory . --ruby-versions 3.3,3.4 --build

Fixes oxidize-rb/actions#27

@ianks ianks merged commit 64a00fd into oxidize-rb:main Jan 14, 2025
56 checks passed
@ianks
Copy link
Collaborator

ianks commented Jan 14, 2025

Released on v0.9.108

@jbourassa jbourassa deleted the rb-sys-dock-pid-host branch January 14, 2025 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Figure out silent process exit on wasmtime-rb
2 participants