@@ -33,19 +33,19 @@ test-unit:
33
33
test-e2e-local :
34
34
# Add the -v flag to observe logs as the run is happening on CI, given that this test takes ~5 minutes to run.
35
35
# Good to have early feedback when needed.
36
- BACKEND=memstore go test -v -timeout 10m ./e2e -parallel 4
36
+ BACKEND=memstore go test -v -timeout 10m ./e2e -parallel 4 | grep -E " ^(--- (PASS|FAIL)|[[:space:]]+(--- PASS|FAIL)) "
37
37
38
38
# E2E tests using holesky testnet backend, leveraging op-e2e framework. Also tests the standard client against the proxy.
39
39
# If holesky tests are failing, consider checking https://dora.holesky.ethpandaops.io/epochs for block production status.
40
40
test-e2e-testnet :
41
- # Add the -v flag to observe logs as the run is happening on CI, given that this test takes ~5 minutes to run.
41
+ # Add the -v flag to observe logs as the run is happening on CI, given that this test takes ~20 minutes to run.
42
42
# Good to have early feedback when needed.
43
- BACKEND=testnet go test -v -timeout 30m ./e2e -parallel 4
43
+ BACKEND=testnet go test -v -timeout 30m ./e2e -parallel 4 | grep -E " ^(--- (PASS|FAIL)|[[:space:]]+(--- PASS|FAIL)) "
44
44
45
45
test-e2e-preprod :
46
- # Add the -v flag to observe logs as the run is happening on CI, given that this test takes ~5 minutes to run.
46
+ # Add the -v flag to observe logs as the run is happening on CI, given that this test takes ~20 minutes to run.
47
47
# Good to have early feedback when needed.
48
- BACKEND=preprod go test -v -timeout 30m ./e2e -parallel 4
48
+ BACKEND=preprod go test -v -timeout 30m ./e2e -parallel 4 | grep -E " ^(--- (PASS|FAIL)|[[:space:]]+(--- PASS|FAIL)) "
49
49
50
50
# Very simple fuzzer which generates random bytes arrays and sends them to the proxy using the standard client.
51
51
# To clean the cached corpus, run `go clean -fuzzcache` before running this.
0 commit comments