-
Notifications
You must be signed in to change notification settings - Fork 710
fix: build backward compatible test contract #13576
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
Conversation
59b193f
to
2a20c83
Compare
@nagisa could you please suggest how |
2a20c83
to
f738125
Compare
f738125
to
fcfba31
Compare
Given that all that's changing here is the list of imported functions IMO its perfectly fine to just update hashes without taking any other action. |
31cbf2a
to
a5515d6
Compare
@nagisa unfortunately |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #13576 +/- ##
=======================================
Coverage 69.47% 69.47%
=======================================
Files 856 856
Lines 168134 168137 +3
Branches 168134 168137 +3
=======================================
+ Hits 116805 116808 +3
- Misses 46544 46548 +4
+ Partials 4785 4781 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
About the rest of the changes, they look alright to me. I'll let someone from CRT have the final say though
Co-authored-by: Simonas Kazlauskas <git@kazlauskas.me>
Currently we copy
backwards_compatible_rs_contract.wasm
fromres
directory. This is no longer necessary since we no longer support old protocol versions.This PR changes that to make it compiled from
test-contract-rs
withoutlatest_protocol
feature enabled. This way we can make changes test contract in backward compatible way using#[cfg(feature = "latest_protocol")]
.backwards_compatible_rs_contract.wasm
is renamed tolegacy_backwards_compatible_rs_contract.wasm
, we keep it for thetest_near_vm_artifact_output_stability
test.We also change
resharding_v3
tests to usebackwards_compatible_rs_contract
instead ofrs_contract
because that test suite uses non-latest protocol version. So it imports host functions that might not yet be exposed in that protocol version which breaks it (#13565 is one example). Backward compatible contract should be used in such cases.