-
Notifications
You must be signed in to change notification settings - Fork 22
improve ci test stability #587
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit a3341bd:
|
c1a9757
to
1dbb21d
Compare
358ed90
to
838fd8c
Compare
.changeset/mighty-cycles-press.md
Outdated
--- | ||
"@turnkey/eip-1193-provider": patch | ||
--- | ||
|
||
Tweak unit tests given expectation that the wallet ID used for tests will have 2 associated addresses |
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.
Nit: if it's a test-only change and doesn't impact the code that our customers consume whatsoever there's no need for a changelog entry 💅
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.
sahweet! removed :)
597ba49
to
a3341bd
Compare
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.
CI 😵
Summary & Motivation
$title
Viem tests were very unstable in CI, particularly due to the ERC721 case. Specifically, there were instances where there would be EVM collisions due to the ERC721 contract being deployed, deterministically, to the same address each time. (address and nonce are factors in determining the contract address. You cannot pass a
salt
during contract deployment using viem at this time)This PR aims to improve test stability by:
Interestingly, these race conditions do not happen locally.
If I were to test something else out, there are the following options:
How I Tested These Changes
local, CI
Did you add a changeset?
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run
pnpm changeset
.pnpm changeset
will generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.