e2e-regression: Use block range in Eden

oasisprotocol · Dec 22, 2023 · dd44d94 · dd44d94
1 parent 6d23919
commit dd44d94
Show file tree

Hide file tree

Showing 74 changed files with 67,627 additions and 65,544 deletions.
diff --git a/tests/e2e_regression/e2e_config_1.yml b/tests/e2e_regression/e2e_config_1.yml
@@ -11,20 +11,23 @@ analysis:
     cache: { cache_dir: tests/e2e_regression/rpc-cache }
     chain_name: mainnet
     nodes:
-      damask:
-        default: { rpc: unix:/tmp/node.sock }
+      # Node will be accessed only when the filling up the cache.
+      # In CI, the cache is expected to have all the node responses as the node is not reachable.
+      eden: { default: { rpc: grpc.oasis.dev:443 } }
     ipfs:
       gateway: https://ipfs.io
     fast_startup: true
   analyzers:
     consensus:
-      from: 8_048_956  # Damask genesis
-      to: 8_049_955    # 1000 blocks; compromise between fast and comprehensive
+      from: 16_817_956  # Eden genesis
+      to: 16_818_955    # 1000 blocks; compromise between fast and comprehensive
     emerald:
-      from: 1_003_298  # round at Damask genesis
-      to: 1_004_297    # 1000 blocks; compromise between fast and comprehensive
-    # sapphire: # Not tested. Does not use much code that is not covered by emerald.
-    #   from: 0  # first round in Damask
+      #from: 7_875_130  # round at Eden genesis, plus 1 (so that in finalizeFastSync we don't need Damask)
+      #to: 7_876_129    # 1000 blocks; compromise between fast and comprehensive
+      from: 8_059_340  # An NFT was created at 8059343; ERC20s were created at 7984382, 7984824, 8075695, 8166988
+      to: 8_060_339    # 1000 blocks; compromise between fast and comprehensive
+    # We do not test Sapphire; the node only makes recent rounds queryable, so it's awkward to test reproducibly.
+    # Also, sapphire does not use much code that is not covered by emerald.
   storage:
     backend: postgres
     endpoint: postgresql://rwuser:password@localhost:5432/indexer?sslmode=disable

diff --git a/tests/e2e_regression/e2e_config_2.yml b/tests/e2e_regression/e2e_config_2.yml
@@ -5,22 +5,16 @@ analysis:
     cache: { cache_dir: tests/e2e_regression/rpc-cache }
     chain_name: mainnet
     nodes:
-      damask:
-        default: { rpc: unix:/tmp/node.sock }
+      eden: { default: { rpc: grpc.oasis.dev:443 } }
     ipfs:
       gateway: https://ipfs.io
     fast_startup: true
   analyzers:
-    evm_tokens_emerald:
-      stop_on_empty_queue: true
-    evm_nfts_emerald:
-      stop_on_empty_queue: true
-    evm_token_balances_emerald:
-      stop_on_empty_queue: true
-    evm_contract_code_emerald:
-      stop_on_empty_queue: true
-    evm_abi_emerald:
-      stop_on_empty_queue: true
+    evm_tokens_emerald:         { stop_on_empty_queue: true }
+    evm_nfts_emerald:           { stop_on_empty_queue: true }
+    evm_token_balances_emerald: { stop_on_empty_queue: true }
+    evm_contract_code_emerald:  { stop_on_empty_queue: true }
+    evm_abi_emerald:            { stop_on_empty_queue: true }
     # Some non-block analyzers are not tested in e2e regressions.
     # They are largely not worth the trouble as they do not interact with rest of the system much.
     # metadata_registry: {} # Awkward to inject mock registry responses.