Add symbol to do general host interface tests #115
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The aim of this PR is to introduce a new API call in the host interface for testing purposes:
__faasm_host_interface_test(int testNum).We need such an API to test specific behaviours of the implementation of the host interface. For example, testing that we can catch an exception from the Faasm runtime thrown from a host-interface function. For more reference on this particular example see faasm/faasm#756.
Annoyingly, the test number enum needs to be shared both by WASM code (that calls the tests by name), and the host interface function's implementation (e.g. in WAVM or in WAMR). Thus, the header needs to be duplicated in the faasm repo.