0xPolygonHermez · tclemos · Mar 7, 2023 · Feb 6, 2023 · Feb 7, 2023 · Feb 8, 2023
diff --git a/.github/workflows/test-e2e.yml b/.github/workflows/test-e2e.yml
@@ -20,7 +20,7 @@ jobs:
       matrix:
         go-version: [ 1.18.x ]
         goarch: [ "amd64" ]
-        e2e-group: [ 1, 2, 3, 4 ]
+        e2e-group: [ 1, 2, 3, 4, 5 ]
     runs-on: ubuntu-latest
     steps:
     - name: Checkout code
@@ -59,7 +59,7 @@ jobs:
       matrix:
         go-version: [ 1.18.x ]
         goarch: [ "amd64" ]
-        e2e-group: [ 1, 2, 3, 4 ]
+        e2e-group: [ 1, 2, 3, 4, 5 ]
     runs-on: ubuntu-latest
     steps:
     - name: Fork based /ok-to-test checkout

@@ -0,0 +1 @@
+../../test/e2e/debug_test.go
@@ -0,0 +1 @@
+../../test/e2e/shared.go
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -93,10 +93,7 @@ services:
 
   zkevm-prover:
     container_name: zkevm-prover
-    image: hermeznetwork/zkevm-prover:798d9e0
-    depends_on:
-      zkevm-state-db:
-        condition: service_healthy
+    image: hermeznetwork/zkevm-prover:1d31dc6
     ports:
       - 50061:50061 # MT
       - 50071:50071 # Executor

@@ -10,7 +10,7 @@ We have 3 different github actions workflows:
 * `test-e2e`, which uses a matrix strategy to run the e2e tests, currently using
 3 groups.
 
-The e2e CI groups are defined in the `./ci/e2e-group{1,3}` directories. In each
+The e2e CI groups are defined in the `./ci/e2e-group{1,N}` directories. In each
 directory we have symlinks that point to the actual e2e test to be executed (these
 tests are defined under `./test/e2e`). The goal of these symlinks is keeping the
 same code organization we have now while being able to run the costly e2e tests