feat(op-acceptance-tests): flashblocks streaming acceptance-tests

[yashvardhan-kukreja]

Signed-off-by: Yashvardhan Kukreja [email protected]

Description

This acceptance-test:

• Goes through every rbuilder and parses its associated conductor
• If that conductor is a non-leader (follower), it establishes a websocket connection to the rbuilder asserting no production of flashblocks from there
• If that conductor is a leader, it establishes a websocket connection to the rbuilder asserting the production of flashblocks from it.
• The flashblocks production is inspected for 5s expecting a total of 17 flashblocks streamed atleast. This number is derived from the expectation of getting flashblocks generated at a 250ms rate (20 flashblocks in 5s) with a tolerance of 3 blocks being slow/dropped (20-3 = 17)

Tests

1. Generate the devnet file via netchef

export MANIFEST=$HOME/OPLabs/Projects/devnets/alphanets/interop-flash/manifest.yaml               
export INVENTORY=$HOME/OPLabs/Projects/devnets/alphanets/interop-flash/inventory.yaml
export DEPLOYER_STATE=$HOME/OPLabs/Projects/devnets/alphanets/interop-flash/op-deployer/state.json
export K8S_REPO=$HOME/OPLabs/Projects/k8s 

cd /path/to/infrastructure-services
cd netchef
just build
./bin/netchef generate --manifest $MANIFEST --inventory $INVENTORY --deployer-state $DEPLOYER_STATE --k8s-dir $K8S_REPO devnet-env

Say the devnet env is generated at /Users/ykukreja/OPLabs/Projects/infrastructure-services/netchef/devnet-tmp/devnet-env.json

2. Point to that devnet env and run these acceptance tests

cd /path/to/optimism
cd op-acceptance-tests
cd tests/flashblocks && \
DEVSTACK_ORCHESTRATOR=sysext \
DEVNET_ENV_URL="/Users/ykukreja/OPLabs/Projects/infrastructure-services/netchef/devnet-tmp/devnet-env.json" \
go test -v -timeout=5m0s -run=TestFlashblocksStream

Here's how it worked on my end

Related Issue

[scharissis]

huh?

[yashvardhan-kukreja]

Currently, sysgo as well as Kurtosis don't implement Flashblocks.
So CI would fail.

So, if you notice the make go-test-ci and make go-test-ci-short Makefile targets, you'll see both of them ending with -tags="ci" which makes them run test in files either with //go:build ci or no mention any //go:build.

By introducing //go:build !ci in this file (along with base/conductor/leadership_transfer_test.go), we're skipping the tests in these files to be run by make go-test-ci / make go-test-ci-short.

Also, //go:build !ci means that when those make targets don't specify any tag filter (-tags="ci"), then the default nature of these test files with //go:build !ci would be to run as opposed to getting skipped when they're target without ! like //go:build foo or //go:build ci

Hope that makes sense.