search

gotestyourself / gotestsum

'go test' runner with output optimized for humans, JUnit XML for CI integration, and a summary of the test results.
Apache License 2.0
1.99k stars 118 forks source link

gotestsum slow in dind container #376

Closed SaiTejaSuvvari closed 9 months ago

SaiTejaSuvvari commented 9 months ago

I was trying to setup integration in github via github workflow.

Im building a test container inside a runner(docker container using dind image) This test container pulls all go dependencies and starts a test using gotestsum. This took around 10 minutes to start the test.

Instead of doing this, I build the test package in the dind container and started the test program inside the test container. This took barely a minute. Any reason as to why this is happening?

I get that building inside a container is slow. This test program actually build binaries for other large services which took around 2-2.5 minutes. But it took around 10 minutes to start a simple test inside the container.

Is it because of the implementation of gotestsum?

dnephin commented 9 months ago

Hello, I am not aware of anything in gotestsum that would make it much slower in a docker-in-docker build. Is it possible something else change between these two setups that made it faster?

If you're able to share a link or some code that demonstrates the problem I can investigate further.

SaiTejaSuvvari commented 9 months ago

I think i found the difference. For the binaries built inside the container, build cache was already available which was missing for the test program. Will use the same using build cache for the test program as well. Closing the issue.