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.

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

Sync interop tests #3156

Merged
merged 5 commits into from
Oct 24, 2024
Merged

Sync interop tests #3156

merged 5 commits into from
Oct 24, 2024

Conversation

JackHamer09
Copy link
Member

No description provided.

Copy link
Contributor

github-actions bot commented Oct 23, 2024

Hey there! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Examples of valid PR titles:

  • feat(eth_sender): Support new transaction type
  • fix(state_keeper): Correctly handle edge case
  • ci: Add new workflow for linting

Details:

No release type found in pull request title "Sync interop tests". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

interop2: string;
};
};
let tokenB_details: {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tokenDetails struct should be used

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

export interface Token {
name: string;
symbol: string;
decimals: bigint;
l1Address: string;
l2Address_1: string;
l2Address_2:string;
assetId: string;
}

const timeout = 10000;

// Interop1 (Main Chain) Variables
let interop1_provider: zksync.Provider;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe chain1 is a better name? but its just a nit

to: interop2_wallet.address,
approveERC20: true,
approveBaseERC20: true,
approveOverrides: { gasPrice },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

formatting weird here

l1Bridgehub = new ethers.Contract(l1BridgehubAddress, bridgehubInterface, l1Wallet);
const chainAddress = await l1Bridgehub.getHyperchain(secondChainId);

tokenDetails = testMaster.environment().erc20Token;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This tokenDetails

@kelemeno kelemeno merged commit f2522c9 into kl/interop-support Oct 24, 2024
26 of 33 checks passed
@kelemeno kelemeno deleted the sync-interop-tests branch October 24, 2024 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants