Skip to content
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.

Sign up for GitHub

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

Jump to bottom

matching versions warnings when running tests #80

Open
gilescope opened this issue Nov 14, 2022 · 0 comments
Open

matching versions warnings when running tests #80

gilescope opened this issue Nov 14, 2022 · 0 comments

Comments

@gilescope
Copy link
Contributor

Started seeing this kind of thing in the tests:

                2022-11-14 13:23:36        API/INIT: Not decorating runtime apis without matching versions: TransactionPaymentApi/2 (1 known), TransactionPaymentCallApi/2 (1 known)
                2022-11-14 13:23:36        API/INIT: Not decorating runtime apis without matching versions: TransactionPaymentApi/2 (1 known), TransactionPaymentCallApi/2 (1 known)
                2022-11-14 13:23:36        API/INIT: Not decorating runtime apis without matching versions: TransactionPaymentApi/2 (1 known), TransactionPaymentCallApi/2 (1 known)
                2022-11-14 13:23:48        API/INIT: Not decorating runtime apis without matching versions: TransactionPaymentApi/2 (1 known), TransactionPaymentCallApi/2 (1 known)
                2022-11-14 13:23:48        API/INIT: Not decorating runtime apis without matching versions: TransactionPaymentApi/2 (1 known), TransactionPaymentCallApi/2 (1 known)
                2022-11-14 13:23:48        API/INIT: Not decorating runtime apis without matching versions: TransactionPaymentApi/2 (1 known), TransactionPaymentCallApi/2 (1 known)
                2022-11-14 13:23:48        API/INIT: Not decorating runtime apis without matching versions: TransactionPaymentApi/2 (1 known), TransactionPaymentCallApi/2 (1 known)

Maybe parachains-integration-test runner should try and update itself before running or complain if out of date / say how to upgrade itself?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gilescope