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

fix: Stress test refactor #1501

Merged
merged 14 commits into from
Jan 22, 2024
Merged

fix: Stress test refactor #1501

merged 14 commits into from
Jan 22, 2024

Conversation

kevinssgh
Copy link
Contributor

Description

Enabled stress test cmd in smoketest

Closes:

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

  • Tested CCTX in localnet
  • Tested in development environment
  • Go unit tests
  • Go integration tests
  • Tested via GitHub Actions

Checklist:

  • I have added unit tests that prove my fix feature works

Copy link

github-actions bot commented Dec 22, 2023

!!!WARNING!!!
nosec detected in the following files: cmd/zetae2e/stress.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

@github-actions github-actions bot added the nosec label Dec 22, 2023
@kevinssgh kevinssgh marked this pull request as ready for review December 22, 2023 19:56
Copy link
Member

@lumtis lumtis left a comment

Choose a reason for hiding this comment

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

We can use functions in cmd/zetae2e/config to simplify runner initialization.

It's also a bit unclear if it is for local testing or live networks. Some of the code implies it's for localnet, but we also provide RPC endpoints as flag option.

changelog.md Outdated Show resolved Hide resolved
cmd/zetae2e/init.go Outdated Show resolved Hide resolved
@kevinssgh
Copy link
Contributor Author

We can use functions in cmd/zetae2e/config to simplify runner initialization.

It's also a bit unclear if it is for local testing or live networks. Some of the code implies it's for localnet, but we also provide RPC endpoints as flag option.

The cmd should be able to do both, depending on the network flag. I mentioned in some of the comments that, it will be useful to make make sure the test is working correctly locally before attempting to run on an external network. This can save some time and effort if there are minor issues.

@kevinssgh kevinssgh requested a review from lumtis January 18, 2024 16:49
@lumtis
Copy link
Member

lumtis commented Jan 22, 2024

@kevinssgh testing the command locally, is this normal logs? The tx number per min seems low to me

orchestrator  | waiting for geth RPC to start...
orchestrator  | funding deployer address 0xE5C5367B8224807Ac2207d350E60e1b6F27a7ecC with 100 Ether
orchestrator  | "0x951014dc646e3fe0151c1a2b3b32a565d702bec8d6afbdabc66b8380eebcc1f9"
orchestrator  | funding deployer address 0x6F57D5E7c6DBb75e59F1524a3dE38Fc389ec5Fd6 with 100 Ether
orchestrator  | "0x7dcafd6d33614630e0b3123b82c995001be059bf45a675e48b34862b2d4a26ac"
orchestrator  | funding deployer address 0x5cC2fBb200A929B372e3016F1925DcF988E081fd with 100 Ether
orchestrator  | "0x6858ce5eaafc887bd1634e8fe2334966f43c43fec2e6ced17a3b4de6a539d3c2"
orchestrator  | funding deployer address 0x283d810090EdF4043E75247eAeBcE848806237fD with 100 Ether
orchestrator  | "0x79eeba9298312ead40f4b659f4ba0b5add1ae1c2b874b3db2d594e4693dfaff0"
orchestrator  | funding deployer address 0x8D47Db7390AC4D3D449Cc20D799ce4748F97619A with 100 Ether
orchestrator  | "0xa57819db484f9401e1cc2c64880911137c8db09a73dab12cb162346ee44ab30f"
orchestrator  | funding deployer address 0x90126d02E41c9eB2a10cfc43aAb3BD3460523Cdf with 100 Ether
orchestrator  | "0xcc526d34be6820549b5bdb21901f35dda4cfea8a3c4237d551e4a87e07b720fe"
orchestrator  | funding deployer address 0xcC8487562AAc220ea4406196Ee902C7c076966af with 100 Ether
orchestrator  | "0xbc354ecce070548130c7f99cb90792866f993082ddbabd7101c95a31efea8b67"
orchestrator  | funding TSS address 0xF421292cb0d3c97b90EEEADfcD660B893592c6A2 with 100 Ether
orchestrator  | "0x987c17ea37339fe44ca848af147a0e7ac09fe374b90e494008e51d0d113880fc"
orchestrator  | running e2e tests...
orchestrator  | Deployer address: 0xE5C5367B8224807Ac2207d350E60e1b6F27a7ecC, balance: 0 Wei
orchestrator  | Last ZetaHeight: 5
orchestrator  | Last ZetaHeight: 8
orchestrator  | Last ZetaHeight: 10
orchestrator  | Last ZetaHeight: 12
orchestrator  | Last ZetaHeight: 14
orchestrator  | Last ZetaHeight: 16
orchestrator  | Last ZetaHeight: 18
orchestrator  | Last ZetaHeight: 20
orchestrator  | Last ZetaHeight: 22
orchestrator  | Last ZetaHeight: 24
orchestrator  | Last ZetaHeight: 26
orchestrator  | Last ZetaHeight: 28
orchestrator  | setup      | ⚙️ setting up TSS address
orchestrator  | setup      | ⚙️ setting up Goerli network
orchestrator  | setup      | ⚙️ deploying system contracts and ZRC20s on ZEVM
orchestrator  | setup      | ⏳ depositing Ethers into ZEVM
orchestrator  | setup      | ✅ Ethers deposited in 4.01319746s
orchestrator  | setup      | ⏳ depositing ZETA into ZEVM
orchestrator  | setup      | ✅ ZETA deposited in 8.042204753s
orchestrator  | eth zrc20 balance: 1000000000000000000 Wei
orchestrator  | approving ETH ZRC20...
orchestrator  | eth zrc20 approve receipt: status 1
orchestrator  | **** STRESS TEST BEGINS ****
orchestrator  | 	1. Periodically Withdraw ETH from ZEVM to EVM - goerli
orchestrator  | 	2. Display Network metrics to monitor performance [Num Pending outbound tx], [Num Trackers]
orchestrator  | pending nonces 0 to 7
orchestrator  | Network Stat => Num of Pending cctx:  8 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 0 to 17
orchestrator  | Network Stat => Num of Pending cctx:  18 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 0 to 26
orchestrator  | Network Stat => Num of Pending cctx:  27 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 0 to 36
orchestrator  | Network Stat => Num of Pending cctx:  37 Num active trackers:  2 Tx Rate:  0  tx/min
orchestrator  | pending nonces 3 to 46
orchestrator  | Network Stat => Num of Pending cctx:  44 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 56
orchestrator  | Network Stat => Num of Pending cctx:  54 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 65
orchestrator  | Network Stat => Num of Pending cctx:  63 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 75
orchestrator  | Network Stat => Num of Pending cctx:  73 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 86
orchestrator  | Network Stat => Num of Pending cctx:  84 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 95
orchestrator  | Network Stat => Num of Pending cctx:  93 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 105
orchestrator  | Network Stat => Num of Pending cctx:  103 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 115
orchestrator  | Network Stat => Num of Pending cctx:  113 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 125
orchestrator  | Network Stat => Num of Pending cctx:  123 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 135
orchestrator  | Network Stat => Num of Pending cctx:  133 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 144
orchestrator  | Network Stat => Num of Pending cctx:  142 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 154
orchestrator  | Network Stat => Num of Pending cctx:  152 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 164
orchestrator  | Network Stat => Num of Pending cctx:  162 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 3 to 174
orchestrator  | Network Stat => Num of Pending cctx:  172 Num active trackers:  3 Tx Rate:  0  tx/min
orchestrator  | pending nonces 3 to 184
orchestrator  | Network Stat => Num of Pending cctx:  179 Num active trackers:  1 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 193
orchestrator  | Network Stat => Num of Pending cctx:  187 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 203
orchestrator  | Network Stat => Num of Pending cctx:  197 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 213
orchestrator  | Network Stat => Num of Pending cctx:  207 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 223
orchestrator  | Network Stat => Num of Pending cctx:  217 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 233
orchestrator  | Network Stat => Num of Pending cctx:  227 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 248
orchestrator  | Network Stat => Num of Pending cctx:  242 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 257
orchestrator  | Network Stat => Num of Pending cctx:  251 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 267
orchestrator  | Network Stat => Num of Pending cctx:  261 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 277
orchestrator  | Network Stat => Num of Pending cctx:  271 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 286
orchestrator  | Network Stat => Num of Pending cctx:  280 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 296
orchestrator  | Network Stat => Num of Pending cctx:  290 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 306
orchestrator  | Network Stat => Num of Pending cctx:  300 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 316
orchestrator  | Network Stat => Num of Pending cctx:  310 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 326
orchestrator  | Network Stat => Num of Pending cctx:  320 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 335
orchestrator  | Network Stat => Num of Pending cctx:  329 Num active trackers:  1 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 345
orchestrator  | Network Stat => Num of Pending cctx:  337 Num active trackers:  1 Tx Rate:  0  tx/min
orchestrator  | pending nonces 10 to 354
orchestrator  | Network Stat => Num of Pending cctx:  345 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 10 to 364
orchestrator  | Network Stat => Num of Pending cctx:  355 Num active trackers:  0 Tx Rate:  3  tx/min

@kevinssgh
Copy link
Contributor Author

@kevinssgh testing the command locally, is this normal logs? The tx number per min seems low to me

orchestrator  | waiting for geth RPC to start...
orchestrator  | funding deployer address 0xE5C5367B8224807Ac2207d350E60e1b6F27a7ecC with 100 Ether
orchestrator  | "0x951014dc646e3fe0151c1a2b3b32a565d702bec8d6afbdabc66b8380eebcc1f9"
orchestrator  | funding deployer address 0x6F57D5E7c6DBb75e59F1524a3dE38Fc389ec5Fd6 with 100 Ether
orchestrator  | "0x7dcafd6d33614630e0b3123b82c995001be059bf45a675e48b34862b2d4a26ac"
orchestrator  | funding deployer address 0x5cC2fBb200A929B372e3016F1925DcF988E081fd with 100 Ether
orchestrator  | "0x6858ce5eaafc887bd1634e8fe2334966f43c43fec2e6ced17a3b4de6a539d3c2"
orchestrator  | funding deployer address 0x283d810090EdF4043E75247eAeBcE848806237fD with 100 Ether
orchestrator  | "0x79eeba9298312ead40f4b659f4ba0b5add1ae1c2b874b3db2d594e4693dfaff0"
orchestrator  | funding deployer address 0x8D47Db7390AC4D3D449Cc20D799ce4748F97619A with 100 Ether
orchestrator  | "0xa57819db484f9401e1cc2c64880911137c8db09a73dab12cb162346ee44ab30f"
orchestrator  | funding deployer address 0x90126d02E41c9eB2a10cfc43aAb3BD3460523Cdf with 100 Ether
orchestrator  | "0xcc526d34be6820549b5bdb21901f35dda4cfea8a3c4237d551e4a87e07b720fe"
orchestrator  | funding deployer address 0xcC8487562AAc220ea4406196Ee902C7c076966af with 100 Ether
orchestrator  | "0xbc354ecce070548130c7f99cb90792866f993082ddbabd7101c95a31efea8b67"
orchestrator  | funding TSS address 0xF421292cb0d3c97b90EEEADfcD660B893592c6A2 with 100 Ether
orchestrator  | "0x987c17ea37339fe44ca848af147a0e7ac09fe374b90e494008e51d0d113880fc"
orchestrator  | running e2e tests...
orchestrator  | Deployer address: 0xE5C5367B8224807Ac2207d350E60e1b6F27a7ecC, balance: 0 Wei
orchestrator  | Last ZetaHeight: 5
orchestrator  | Last ZetaHeight: 8
orchestrator  | Last ZetaHeight: 10
orchestrator  | Last ZetaHeight: 12
orchestrator  | Last ZetaHeight: 14
orchestrator  | Last ZetaHeight: 16
orchestrator  | Last ZetaHeight: 18
orchestrator  | Last ZetaHeight: 20
orchestrator  | Last ZetaHeight: 22
orchestrator  | Last ZetaHeight: 24
orchestrator  | Last ZetaHeight: 26
orchestrator  | Last ZetaHeight: 28
orchestrator  | setup      | ⚙️ setting up TSS address
orchestrator  | setup      | ⚙️ setting up Goerli network
orchestrator  | setup      | ⚙️ deploying system contracts and ZRC20s on ZEVM
orchestrator  | setup      | ⏳ depositing Ethers into ZEVM
orchestrator  | setup      | ✅ Ethers deposited in 4.01319746s
orchestrator  | setup      | ⏳ depositing ZETA into ZEVM
orchestrator  | setup      | ✅ ZETA deposited in 8.042204753s
orchestrator  | eth zrc20 balance: 1000000000000000000 Wei
orchestrator  | approving ETH ZRC20...
orchestrator  | eth zrc20 approve receipt: status 1
orchestrator  | **** STRESS TEST BEGINS ****
orchestrator  | 	1. Periodically Withdraw ETH from ZEVM to EVM - goerli
orchestrator  | 	2. Display Network metrics to monitor performance [Num Pending outbound tx], [Num Trackers]
orchestrator  | pending nonces 0 to 7
orchestrator  | Network Stat => Num of Pending cctx:  8 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 0 to 17
orchestrator  | Network Stat => Num of Pending cctx:  18 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 0 to 26
orchestrator  | Network Stat => Num of Pending cctx:  27 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 0 to 36
orchestrator  | Network Stat => Num of Pending cctx:  37 Num active trackers:  2 Tx Rate:  0  tx/min
orchestrator  | pending nonces 3 to 46
orchestrator  | Network Stat => Num of Pending cctx:  44 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 56
orchestrator  | Network Stat => Num of Pending cctx:  54 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 65
orchestrator  | Network Stat => Num of Pending cctx:  63 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 75
orchestrator  | Network Stat => Num of Pending cctx:  73 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 86
orchestrator  | Network Stat => Num of Pending cctx:  84 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 95
orchestrator  | Network Stat => Num of Pending cctx:  93 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 105
orchestrator  | Network Stat => Num of Pending cctx:  103 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 115
orchestrator  | Network Stat => Num of Pending cctx:  113 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 125
orchestrator  | Network Stat => Num of Pending cctx:  123 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 135
orchestrator  | Network Stat => Num of Pending cctx:  133 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 144
orchestrator  | Network Stat => Num of Pending cctx:  142 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 154
orchestrator  | Network Stat => Num of Pending cctx:  152 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 3 to 164
orchestrator  | Network Stat => Num of Pending cctx:  162 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 3 to 174
orchestrator  | Network Stat => Num of Pending cctx:  172 Num active trackers:  3 Tx Rate:  0  tx/min
orchestrator  | pending nonces 3 to 184
orchestrator  | Network Stat => Num of Pending cctx:  179 Num active trackers:  1 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 193
orchestrator  | Network Stat => Num of Pending cctx:  187 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 203
orchestrator  | Network Stat => Num of Pending cctx:  197 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 213
orchestrator  | Network Stat => Num of Pending cctx:  207 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 223
orchestrator  | Network Stat => Num of Pending cctx:  217 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 233
orchestrator  | Network Stat => Num of Pending cctx:  227 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 248
orchestrator  | Network Stat => Num of Pending cctx:  242 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 257
orchestrator  | Network Stat => Num of Pending cctx:  251 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 267
orchestrator  | Network Stat => Num of Pending cctx:  261 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 277
orchestrator  | Network Stat => Num of Pending cctx:  271 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 286
orchestrator  | Network Stat => Num of Pending cctx:  280 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 296
orchestrator  | Network Stat => Num of Pending cctx:  290 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 306
orchestrator  | Network Stat => Num of Pending cctx:  300 Num active trackers:  0 Tx Rate:  4  tx/min
orchestrator  | pending nonces 7 to 316
orchestrator  | Network Stat => Num of Pending cctx:  310 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 326
orchestrator  | Network Stat => Num of Pending cctx:  320 Num active trackers:  0 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 335
orchestrator  | Network Stat => Num of Pending cctx:  329 Num active trackers:  1 Tx Rate:  0  tx/min
orchestrator  | pending nonces 7 to 345
orchestrator  | Network Stat => Num of Pending cctx:  337 Num active trackers:  1 Tx Rate:  0  tx/min
orchestrator  | pending nonces 10 to 354
orchestrator  | Network Stat => Num of Pending cctx:  345 Num active trackers:  0 Tx Rate:  3  tx/min
orchestrator  | pending nonces 10 to 364
orchestrator  | Network Stat => Num of Pending cctx:  355 Num active trackers:  0 Tx Rate:  3  tx/min

Yes, locally it is much slower than the real network. You also have to remember this is outbound txn rate which takes some time based on the scheduler.

Copy link
Member

@lumtis lumtis left a comment

Choose a reason for hiding this comment

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

Ok, let's merge so we can sync we the other changes on the other PR

Copy link
Contributor

@kingpinXD kingpinXD left a comment

Choose a reason for hiding this comment

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

It looks good to me ,
Curious though why are we using a withdraw only for the trees test , because the withdraw would be limited by the outbound TSS signing , which we already know .
Is the purpose only to add more transactions into the cosmos mempool ?

It might be a good idea to consider lowering the rate for withdraws and add some more transactions into the mix , we can create inbounds , or even bank sends back and forth between two accounts , which might be a more realistic simulation

@kevinssgh
Copy link
Contributor Author

It looks good to me , Curious though why are we using a withdraw only for the trees test , because the withdraw would be limited by the outbound TSS signing , which we already know . Is the purpose only to add more transactions into the cosmos mempool ?

It might be a good idea to consider lowering the rate for withdraws and add some more transactions into the mix , we can create inbounds , or even bank sends back and forth between two accounts , which might be a more realistic simulation

The idea behind this stress test was to test the bottleneck in the network which is outbound withdraws. We can add more to this test in the future for sure as well.

@kevinssgh kevinssgh merged commit 04e0129 into develop Jan 22, 2024
15 checks passed
@kevinssgh kevinssgh deleted the stress-test-refactor branch January 22, 2024 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants