> On 24 Oct 2020, at 22.21, Craig Silverstein <csilv...@khanacademy.org> wrote:
>
>> Client:
>> FOR EACH pkg in pkgs DO
>> (1) result := "go test "+ $pkg;
>> (2) POST /$pkg/$result
>> DONE
>
> As I mentioned above: we can certainly do things this way, but there's
> a big performance hit to invoking `go test` repeatedly.
Oh, I see. Have you try turn off vet doing test? Probably there are other
build/test flags that can also be turned off which I am not aware to speeding
test up.
>
> To be clear, I'm not suggesting changing `go test`. My first idea was
> to write our own tool, that calls out to the API in
> https://golang.org/pkg/testing/ to do the actual mechanics of testing.
> But that API doesn't seem to be designed to allow such a thing -- as
> one example, the `go test` commandline tool seems to do a lot of work
> itself, that our tool would need to duplicate -- and it's unclear how
> practical it is to force it. There may well be better ideas we don't
> know enough to even think of, though.
Another solution that I can think of is by building each package tests binaries
in server and distributed it to test machines, so the client does not need to
re-build (file read/write, compile, linking, and so on).
--
Shulhan
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/98963401-FA64-40E1-8833-83F9EA1B7CCA%40gmail.com.
