Skip to content

Commit 4c23b9d

Browse files
authored
chore: Deflake epochs_proof_public_cross_chain test (#19202)
This test was using a deprecated helper for checking when an L1 to L2 message was ready for consumption. Let's see if updating it to the correct helper makes a difference. Failed run: http://ci.aztec-labs.com/56900023bee935c0
2 parents 19b00c9 + 05895c1 commit 4c23b9d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

yarn-project/end-to-end/src/e2e_epochs/epochs_proof_public_cross_chain.test.ts

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
import { generateClaimSecret } from '@aztec/aztec.js/ethereum';
22
import { Fr } from '@aztec/aztec.js/fields';
33
import type { Logger } from '@aztec/aztec.js/log';
4+
import { waitForL1ToL2MessageReady } from '@aztec/aztec.js/messaging';
45
import { TxStatus } from '@aztec/aztec.js/tx';
56
import { EthAddress } from '@aztec/foundation/eth-address';
67
import { retryUntil } from '@aztec/foundation/retry';
@@ -51,11 +52,10 @@ describe('e2e_epochs/epochs_proof_public_cross_chain', () => {
5152
const { msgHash, globalLeafIndex } = await sendL1ToL2Message(message, context.deployL1ContractsValues);
5253

5354
logger.warn(`Waiting for message ${msgHash} with index ${globalLeafIndex} to be synced`);
54-
await retryUntil(
55-
() => context.aztecNode.isL1ToL2MessageSynced(msgHash),
56-
'message sync',
57-
test.L2_SLOT_DURATION_IN_S * 4,
58-
);
55+
await waitForL1ToL2MessageReady(context.aztecNode, msgHash, {
56+
forPublicConsumption: true,
57+
timeoutSeconds: test.L2_SLOT_DURATION_IN_S * 6,
58+
});
5959

6060
// And we consume the message using the test contract. It's important that we don't wait for the membership witness
6161
// to be available, since we want to test the scenario where the message becomes available on the same block the tx lands.

0 commit comments

Comments
 (0)