Restore Bridge CI

[andygolay]

Summary

• RFCs: Link to RFC, Link to RFC, or $\emptyset$.

• Categories: any of protocol-units, networks, scripts, util, cicd, or misc.

• Closed Restore Bridge CI #921 and started a new branch cut from feature/trusted-relayer, due to odd "file not found" errors

Changelog

Testing

Outstanding issues

[andygolay]

After encountering difficulties running the CI (see #921 (comment)), I've taken to attempting to get the tests to pass in process-compose locally.

There are some apaprent inconsistencies locally, for example:

Running a node with

CELESTIA_LOG_LEVEL=FATAL nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash  -c "just bridge native build.setup.eth-local.celestia-local.bridge --keep-tui" 

And running the E2E tests with

RUST_BACKTRACE=1 DOT_MOVEMENT_PATH="$(pwd)/.movement" cargo test --test bridge_e2e_test_framework -- --nocapture --test-threads=1

the tests pass.

However, when I run

CELESTIA_LOG_LEVEL=FATAL nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash  -c "just bridge native build.setup.eth-local.celestia-local.bridge.test --keep-tui" 

with the following process-compose.test.yml:

version: "3"

environment:

processes:
  test_e2e:
    command: |
      DOT_MOVEMENT_PATH="$(pwd)/.movement" cargo test --test bridge_e2e_test_framework -- --nocapture --test-threads=1
    depends_on:
      bridge:
        condition: process_healthy
    availability:
      exit_on_end: false

  test_eth:
    command: |
      DOT_MOVEMENT_PATH="$(pwd)/.movement" cargo test --test client_eth_tests -- --nocapture --test-threads=1
    depends_on:
      bridge:
        condition: process_healthy
    availability:
      exit_on_end: false

  test_mvt:
    command: |
      DOT_MOVEMENT_PATH="$(pwd)/.movement" cargo test --test client_mvt_tests -- --nocapture --test-threads=1
    depends_on:
      bridge:
        condition: process_healthy
    availability:
      exit_on_end: false

The E2E test process fails with mis-matching bridge transfer IDs.