[NONEVM-1612] add bare-bones EVM to TON structure in E2E env
Initial set up of an EVM > TON messaging test to identify missing components. We need to iterate on this as we tackle all the dependencies / blockers until the test eventually passes.
Primary Changes
- Added TON chain generation, management, and client setup using
tonutils-golibrary - Created
cciptonpackage with noop implementations for TON CCIP components - Added
ccipnooppackage with placeholder implementations for all CCIP contract interfaces - Created
NoopTransmittercontract transmitter factory for chains without deployed CCIP contracts - Added
WithTonChains()configuration option and TON-specific test helpers - Added TON keystore integration and transmitter key handling
- Intended failure assertion in
AddLaneis implemented
Dependencies
- [x] https://github.com/smartcontractkit/chainlink/pull/17666
- [x] https://github.com/smartcontractkit/chainlink/pull/17893
- [x] https://github.com/smartcontractkit/chainlink/pull/17946
- [x] https://github.com/smartcontractkit/chainlink/pull/17962
- [x] https://github.com/smartcontractkit/chainlink/pull/17930
- [x] https://github.com/smartcontractkit/chainlink/pull/17706
- [x] https://github.com/smartcontractkit/chainlink/pull/16363
I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:
#addedFor any new functionality added.#breaking_changeFor any functionality that requires manual action for the node to boot.#bugfixFor bug fixes.#changedFor any change to the existing functionality.#db_updateFor any feature that introduces updates to database schema.#deprecation_noticeFor any upcoming deprecation functionality.#internalFor changesets that need to be excluded from the final changelog.#nopsFor any feature that is NOP facing and needs to be in the official Release Notes for the release.#removedFor any functionality/config that is removed.#updatedFor any functionality that is updated.#wipFor any change that is not ready yet and external communication about it should be held off till it is feature complete.
:medal_military: No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.
Another thing, I noticed every time after running the test, it generate node data for the local TON client. We probably want to clean it up after each run. cc @jadepark-dev
Flakeguard Summary
Ran new or updated tests between develop and 8d967d7974e1f655e465fbabd81d790fe9bd4839 (ccip-ton-e2e).
View Flaky Detector Details | Compare Changes
Found Flaky Tests :x:
1 Results
| Name | Pass Ratio | Panicked? | Timed Out? | Race? | Runs | Successes | Failures | Skips | Package | Package Panicked? | Avg Duration | Code Owners |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TestUpdateTokenPriceFeedsFeeQuoterChangeset/MCMS_enabled | 0% | true | true | false | 1 | 0 | 1 | 0 | github.com/smartcontractkit/chainlink/deployment/ccip/changeset/v1_6 | true | 0s | @smartcontractkit/ccip-tooling, @smartcontractkit/ccip-offchain, @smartcontractkit/core, @smartcontractkit/deployment-automation, @smartcontractkit/cld-team |
Artifacts
For detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json.
@patrickhuie19 Any idea why the CODEOWNERS check is failing here? There's lots of errors, most of them not caused by this PR
@patrickhuie19 Any idea why the CODEOWNERS check is failing here? There's lots of errors, most of them not caused by this PR
@archseer handling offline to unblock, but that check should only become required once it passes on a clean PR
Quality Gate passed
Issues
31 New issues
12 Fixed issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
1.1% Duplication on New Code