The newly run chain nodes on the `testnet` cannot synchronize blocks

[0xbillw]

Context environment

1. sudo cess version

    Node mode: rpcnode
    Profile: testnet
    nodeadm version: v0.5.9
    Docker images:
      config-gen: config-gen 1.5.6 6ddc298089eb
      chain: cess-node 0.8.0-7e23e95 68b0f06c97a2
   

2. useful chain container logs

✌️ `cess-node` version: 0.8.0-7e23e95
📋 Chain specification: cess-testnet
👤 Role: FULL
💻 Operating system: linux
💻 CPU architecture: x86_64
💻 Target environment: gnu
💻 CPU: AMD EPYC 7282 16-Core Processor
💻 CPU cores: 4
💻 Memory: 5935MB
💻 Kernel: 5.15.0-25-generic
💻 Linux distribution: Ubuntu 20.04.6 LTS

Problem description

When running a brand new (with empty chain data) RPC node using cess-nodeadm-v0.5.9, an error occurs during synchronization, causing it to become stuck on a specific block and unable to proceed. This is illustrated in the figure below (with sync trace log enabled).

Preliminary analysis indicates that the issue arises from inconsistencies in the results of code execution during the import of block #244, compared to the results at that time. Further investigation suggests that the misuse of SpecVersion and NativeElseWasmExecutor at that time may be the underlying cause.

Expected outcomes

Expect to run the testnet node in a brand new environment.