-
Notifications
You must be signed in to change notification settings - Fork 3.4k
issue/14745 code #14795
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
base: main
Are you sure you want to change the base?
issue/14745 code #14795
Conversation
Thank you for submitting a pull request! If this is your first PR, make sure to add yourself to AUTHORS. |
Sorry for the delay here - @ArthurG0 , this looks good I think. Can you add testing for it? Adding a little to the existing test should be enough, the one under |
Unfortunately, I can't even run the current tests without errors using the command you provided (
is the error. I'm running it on my windows machine on both my own fork as well as main branch of the base repo. Could you comment on this, have you encountered not being able to run the tests? |
That error looks like its because you are using an older version of llvm before we changed the max_align_t. Are you using emsdk to install emscripten? That is the recommended way to be sure you have the correct versions. Alternatively you could build llvm from tip-of-tree. |
Thank you, was able to update LLVM version and run the tests successfully, adding them to the PR |
Looks like the webidl tests fail - hopefully that can be debugged locally? Separately I see other failures, that may indicate this is not rebased on something new enough. Merging in latest |
}; | ||
======= | ||
}; | ||
>>>>>>> 4f765dec0830dce21da8ed2db74ecabbd7a48186 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like a merge error here.
This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant. |
No description provided.