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

Update to Wasmtime 20.0.2 to pass CI #317

Closed

Conversation

jsturtevant
Copy link
Contributor

@jsturtevant jsturtevant commented Jun 21, 2024

This was previously always pulling the dev c api for wasmtime, causing failures on simple PR's like #313.

This temporally disables the dev version of the wasmtime c-api in order to get start making incremental updates as a part of fixing #315

Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
@jsturtevant jsturtevant mentioned this pull request Jun 21, 2024
@jsturtevant
Copy link
Contributor Author

The correct c-api's are now used, but looks like there might have been some other changes required. maybe #316

  Restore was successful.
  Downloading from "https://github.com/bytecodealliance/wasmtime/releases/download/v19.0.1/wasmtime-v19.0.1-x86_64-linux-c-api.tar.xz" to "/home/runner/work/wasmtime-dotnet/wasmtime-dotnet/src/obj/wasmtime-v19.0.1-x86_64-linux-c-api.tar.xz" (13,421,744 bytes).

Signed-off-by: James Sturtevant <jsturtevant@gmail.com>
@jsturtevant jsturtevant changed the title Only run wasmtime dev branch when schedule triggers on Main Update to Wasmtime 20.0.2 to pass CI Jun 22, 2024
@jsturtevant
Copy link
Contributor Author

moved this to a branch via #321

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.

None yet

1 participant