Skip to content

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

@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).

@jsturtevant jsturtevant force-pushed the dont-use-dev-on-prs branch from 5303b84 to a816a0a Compare June 22, 2024 20:04
@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.

1 participant