From f336f34153cb525b5db0595a6dca79b14c15ffd0 Mon Sep 17 00:00:00 2001
From: Santiago Palladino <santiago@aztecprotocol.com>
Date: Wed, 27 Nov 2024 17:03:11 -0300
Subject: [PATCH] chore: Teardown context in prover coordination test

The network from the first test kept running in parallel while the
second one ran. This should not cause issues for the second run since
they use a different rollup contract on L1, but having two anvil test
watchers could be having weird consequences.
---
 .../src/prover-coordination/e2e_prover_coordination.test.ts   | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/yarn-project/end-to-end/src/prover-coordination/e2e_prover_coordination.test.ts b/yarn-project/end-to-end/src/prover-coordination/e2e_prover_coordination.test.ts
index 6ec6832ff53e..bf0cf8934e0f 100644
--- a/yarn-project/end-to-end/src/prover-coordination/e2e_prover_coordination.test.ts
+++ b/yarn-project/end-to-end/src/prover-coordination/e2e_prover_coordination.test.ts
@@ -128,6 +128,10 @@ describe('e2e_prover_coordination', () => {
     await performEscrow(10000000n);
   });
 
+  afterEach(async () => {
+    await snapshotManager.teardown();
+  });
+
   const expectProofClaimOnL1 = async (expected: {
     epochToProve: bigint;
     basisPointFee: number;