-
Notifications
You must be signed in to change notification settings - Fork 943
ci: introduce the deff check for rust #5356
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
ci: introduce the deff check for rust #5356
Conversation
3047a88
to
d58bb1e
Compare
Need to look inside the CI but looks like there is some collision between Valgrind and rust?
|
4cdc56f
to
0ac24b8
Compare
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Trivial Rebase |
0ac24b8
to
a4a7c29
Compare
There is already a target called I opened #5415 as counterproposal :-) |
I admit that I'm not a big fan of mixing required stuff with not required stuff when we are working with not standard build system for the only reason a new dev that did not know how we use rust can fall in some strange error, the #5415 is fair enough to close this! |
This is a monkey patch, just to be sure that we did not release inconsistent code, but we can evaluate to remove the generated file? or make rust a requirements (we all love rust 🦀 )
Updating also some rust model
Rebased on top of #5364
Signed-off-by: Vincenzo Palazzo vincenzopalazzodev@gmail.com