#Go testing in Dagger
1 messages · Page 1 of 1 (latest)
I’ll look at the dagger repo to get some ideas. It’s hard to tell where it’s docker lag/security software on my Mac so I’ll probably spin up a codespace image and compare in a cleaner environment. Do you suppress test output and use artifact to then print output to avoid the buildkit noise?
Yeah, I generally suppress the buildkit output unless I set a debug flag to show it
Any specific examples you’d point to that was optimized? Otherwise will just look at the repo