-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
gas estimator + fee boosting integ test #15208
base: develop
Are you sure you want to change the base?
Conversation
I see you updated files related to
|
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
Flaky Test Detector for
|
Flaky Test Detector for
|
Flaky Test Detector for
|
fbe92fb
to
8eb6bed
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.
Still in progress
80a6aa1
to
020ce58
Compare
020ce58
to
bb18c94
Compare
Hey @0xnogo! I see one job related to detecting flaky tests is failing. The issue may not be related to your PR. I think you can ignore this for now. I'll try to debug it later today. |
} | ||
|
||
func runFeeboostTestCase(tc feeboostTestCase) { | ||
require.NoError(tc.t, ccipdeployment.AddLane(tc.deployedEnv.Env, tc.onchainState, tc.sourceChain, tc.destChain, tc.initialPrices)) |
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.
should this move to test setup better?
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.
We need to pass in the input prices. As mentioned offline, this will change when we will fix the bug in the commit plugin which prevent prices from being published when there is no merkle root
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.
fixed here: smartcontractkit/chainlink-ccip#316
Receiver: common.LeftPadBytes(tc.onchainState.Chains[tc.destChain].Receiver.Address().Bytes(), 32), | ||
Data: []byte("message that needs fee boosting"), | ||
TokenAmounts: nil, | ||
FeeToken: common.HexToAddress("0x0"), |
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.
How's the token address 0x0
?
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.
0x0 = Paying in Eth directly
ccipdeployment.ReplayLogs(tc.t, tc.deployedEnv.Env.Offchain, replayBlocks) | ||
|
||
ccipdeployment.ConfirmCommitForAllWithExpectedSeqNums(tc.t, tc.deployedEnv.Env, tc.onchainState, expectedSeqNum, startBlocks) | ||
ccipdeployment.ConfirmExecWithSeqNrForAll(tc.t, tc.deployedEnv.Env, tc.onchainState, expectedSeqNum, startBlocks) |
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.
Is there a way to assert that the fee was actually boosted with a more accurate measure?
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.
This will come in as a second step. We wanted to increase our coverage first. But there is no easy way of doing it.
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.
I don't think that this is enough as it doesn't really assert that fee boosting was run successfully and the recalculated fees. Approving as you mentioned in our conversation that it's the first iteration and that it's waiting a couple of bug fixes on chainlink-ccip side to be able to continue it properly.
DestGasOverhead
in the gas estimation