ignore the tests that use tessera enclave via docker

[macfarla]

Signed-off-by: Sally MacFarlane sally.macfarlane@consensys.net

These tests are uniformly failing since about 6 hours ago. Docker container startup error. eg

org.testcontainers.containers.ContainerLaunchException: Container startup failed
	at app//org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:345)
	at app//org.testcontainers.containers.GenericContainer.start(GenericContainer.java:326)
	at app//org.hyperledger.enclave.testutil.TesseraTestHarness.start(TesseraTestHarness.java:83)
	at app//org.hyperledger.besu.tests.acceptance.dsl.privacy.PrivacyNode.start(PrivacyNode.java:194)
	at app//org.hyperledger.besu.tests.acceptance.dsl.privacy.PrivacyCluster.startNode(PrivacyCluster.java:182)
	at app//org.hyperledger.besu.tests.acceptance.dsl.privacy.PrivacyCluster.lambda$selectAndStartBootnode$6(PrivacyCluster.java:136)
...
            org.testcontainers.containers.ContainerLaunchException: Could not create/start container

Documentation

• I thought about documentation and added the doc-change-required label to this PR if
  updates are required.

Changelog

• I thought about the changelog and included a changelog update if required.

[freemanzMrojo]

Hi @macfarla ,

Hope you are doing well! Probably you guys have noticed this already, if so please disregard this comment, but it looks like the issue is related to the Docker image of the new Tessera release, 22.1.6.

I have changed the version of the image in my branch for the acceptance tests in TesseraTestHarness (#4282) to 22.1.5 (used to be latest) and the tests are passing (I haven't rebased yet with the latest of main including the changes of this PR).

Would it be possible to just change that version temporarily and re-enable the tests until the solution is found? I could create a PR if you want.

Thanks in advance, Miguel.

[macfarla]

@freemanzMrojo I did suspect the docker image change - but I looked at the Tessera version here https://github.com/hyperledger/besu/pull/4295/files and it was using 22.1.3 - turns out there's two spots where we have the docker version which is not ideal!

PR here #4303

[freemanzMrojo]

Thanks @macfarla !