cost-tracking: add testing infrastructure #680
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this commit we add the infrastructure necessary to test the runtime's cost tracking. We take advantage of the tests that already exist to check the interpreter and the runtime match in the results that they produce, and add an assertion that the tracked costs should also be equivalent.
To trigger the cost tracking tests, a new feature
test-cost-tracking
is added. By default cost tracking checks are not included, to preserve current behavior.We also add the tests to the CI infrastructure, by adding a new matrix field controlling if we test with cost tracking or not.
Resolves: #636