Latest WAMR #650
Merged
Latest WAMR #650
Conversation
This file contains hidden or 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
Shillaker
approved these changes
May 31, 2022
Collaborator
|
Pre-emptively approved this so that you can merge when done. |
d15554b to
f00c70c
Compare
Collaborator
Author
|
@Shillaker it looks as though we may be running out of RAM for the TSAN build :/ The available RAM for Linux GH hosted runners is 7 GB. I have tried increasing the swap space, but we are out of luck running inside a container, and I would be surprised if we could do that in a GitHub hosted runner anyway. Let's discuss offline what's the best way to fix this. |
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.
In this PR I bump the WAMR fork to the latest commit as of today, and cherry pick the codegen fixes from #642. This changes fix the broken tests in #635.
I also cleanup our diff with the upstream WAMR, minimising the changes to only those we need.
I have had to comment out one of the additions in #642, see here. I will get on with the memory growth/shrinking in a separate PR.
Closes #635