Closed dkijania closed 1 week ago
!ci-build-me
@dkijania could you add info on how was this change tested? In particular, I'm interested in confirmations:
@georgeee Apologies for not providing this information earlier. I tested instrumented dockers manually by:
docker pull gcr.io/o1labs-192920/mina-daemon:785dbcf-bullseye-berkeley-instrumented
docker run -it --entrypoint bash gcr.io/o1labs-192920/mina-daemon:785dbcf-bullseye-berkeley-instrumented
mina internal
ls *.coverage
The same test for non-instrumented dockers but effect should be no coverage files. I performed such test for all combination of dockers for daemon and archive node
!ci-build-me
!ci-build-me
We are not distinguishing instrumented docker in CI. This PR is adding
-instrumented
suffix to a daemon and archive docker