-
Notifications
You must be signed in to change notification settings - Fork 526
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
pallet-verifier (milestone 1 & 2) #1222
Conversation
Hey @davidsemakula , |
Hi @PieWol
I'll do the latter and ping you. 🙂 |
Great, thank you :) |
Hi @PieWol
I've added the details to the delivery document. |
Great, thanks. I'll let you know once I made progress on the review. |
@PieWol I pushed a few updates, please pull the latest from master before reviewing 🙂 |
Thanks for the update @davidsemakula :) |
Hey @davidsemakula , See
|
Hi @PieWol |
Pinging @PieWol 🙂 |
@PieWol The suggested cargo config update appears to fix the issue in my testing, so I've pushed an update to master with the fix applied (along with a few other general improvements). |
Thanks, I'll update you later today. |
@davidsemakula |
@PieWol should be fixed, please pull latest |
Hey @davidsemakula , I have put up a draft pr already for the milestone 1 evaluation. Thanks |
Hey @davidsemakula ,
Whats the reason for this error? Is it because the testing functions have different names than the actual calls of the pallet? 🤔 |
@PieWol Checking it out ... the names of the tests shouldn't matter though 🙂 |
Hi @PieWol The issue was this pallet has a cyclic transitive dependency on itself in test mode (via some of its dev dependencies - see also). So our custom rustc driver was being prematurely invoked on this cyclic dependency (instead of the "primary" package - for the compiler, these are different artifacts because of different compiler flags, configs, features et.c). So no unit tests where being found because the test harness (and hence the tests module in this case) is NOT built/compiled for dependencies (only for the "primary" package). I've updated the cargo subcommand to detect these cases and only invoke our custom rustc driver for the right artifact, so it should work fine now (i.e. after pulling and installing latest changes from master). Thanks for finding/reporting the issue 🙂 |
Hey @davidsemakula , |
🪙 Please fill out the invoice form in order to initiate the payment process. Thank you! |
Congratulations on finishing this grant 🎉 . Nice work! |
Thanks for the swift and thorough review @PieWol , and for the positive feedback as well!
This is 100% the plan 🙂 |
I've also submitted the invoices 🙂 |
Milestone Delivery Checklist
Link to the application pull request: w3f/Grants-Program#2234 < please fill this in with the PR number of your application.