- 
        Couldn't load subscription status. 
- Fork 35
Add emscripten automated tests #483
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
Add emscripten automated tests #483
Conversation
| Codecov ReportAll modified and coverable lines are covered by tests ✅ 
 Additional details and impacted files@@           Coverage Diff           @@
##             main     #483   +/-   ##
=======================================
  Coverage   72.71%   72.71%           
=======================================
  Files           9        9           
  Lines        3618     3618           
=======================================
  Hits         2631     2631           
  Misses        987      987           
 
 🚀 New features to boost your workflow:
 | 
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.
clang-tidy made some suggestions
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.
clang-tidy made some suggestions
f3d8b34    to
    e211109      
    Compare
  
    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.
clang-tidy made some suggestions
82343f6    to
    f8250bd      
    Compare
  
    dad83f5    to
    8b62073      
    Compare
  
    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.
clang-tidy made some suggestions
027e9a3    to
    ab5976a      
    Compare
  
    bba850e    to
    123e15c      
    Compare
  
    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.
I am adding a few comments from my partial review.
| 
 In the case of the crashing tests it almost always due to memory access issues. In the case of the few failing tests, the tests do run, but they don't give the result that what is expected. It could be said that in the Emscripten case, a different result is to be expected for some of these tests, but I do not plan to fix the tests as part of this PR. | 
| 
 Also thought I'd mentioned that @Vipul-Cariappa mentioned that the failing tests do give some explanation as to why an Emscripten version of cppyy doesn't work at the moment. I believe he plans to investigate them in the future as part of his work to get a working Emscripten build of cppyy, once he has time. He is busy with other things at the moment though. | 
| Regarding my last 3 reviews. Obviously as you said the goal might not be to get all tests runnings here, so no issues. I am just trying to get an idea on why something would not work. For eg 
 Maybe we might be overlooking something obvious 😬 | 
| Hey @mcbarton I just realized #440 went in. This should also do the job for us and expose all symbols from the C API we need. So we no longer need #518 (and I am closing that issue) Dumping all the symbols should be enough to see that they are being exposed correctly If you rebase your PR on latest main and remove all symbols relevant to the c API (https://github.com/compiler-research/CppInterOp/pull/483/files#diff-054935aee7c0887220251f89b2179dbc4a0c418a69bca9f74854305ae7c0f967R31) P.S: That should leave us with only symbols coming of static libs from clang/llvm | 
54a5b49    to
    57ab2c0      
    Compare
  
    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 okay to me
Description
Please include a summary of changes, motivation and context for this PR.
My first PR to add automated emscripten tests became broken for unknown reasons (see #448). This PR is another attempt to added emscripten tests to CppInterOp
Fixes # (issue)
Type of change
Please tick all options which are relevant.
Testing
Please describe the test(s) that you added and ran to verify your changes.
Checklist