-
Notifications
You must be signed in to change notification settings - Fork 428
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
[FEAT] Create lib_ccxr
and libccxr_exports
#1551
Conversation
lib_ccxr
and libccxr_exports
CCExtractor CI platform finished running the test files on linux. Below is a summary of the test results:
It seems that not all tests were passed completely. This is an indication that the output of some files is not as expected (but might be according to you). Your PR breaks these cases:
Check the result page for more info. |
@cfsmp3 @PunitLodha Are the tests conducted in the sample platform flaky? Because both this PR and #1555 only add some extra rust code and don't export anything for C. Both the PR shouldn't practically change anything and all the tests should execute in the same way. Still the test results differ. How is this possible? |
Ask in slack about the test platform 😁 And please do follow the conversation there about it |
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
This is an attempt to split #1495 into multiple independant PRs.
This is the first PR that sets up the modules structure and their respective cargo toml files. Every upcoming PR for
lib_ccxr
will be dependant on this.