You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We set -p 1 by default for darwin/arm, because it's impossible to run more than one test at a time on the iOS device (each test is packaged as an app for execution).
As a result, stdlib builds also happen one package at a time on the host, which can be a bit frustrating when you're looking for a compiler error.
Just for this I don't think it's worth complicating the go command to separate the notions of parallelism, but if some other changes happen to its work scheduling, parallel darwin/arm builds would be nice to have.
The text was updated successfully, but these errors were encountered:
I think the correct way is to leave -p as is and serialize the running of
tests on android/ios in cmd/go/test.go.
see http://tip.golang.org/src/cmd/go/test.go#L473 for how it could
be done.
Now that darwin/arm no longer use an explicit -p=1 in the go command
remove the explicit -p=<num cpus> from gomobile as well.
While we're here, fix the init test templates to reflect the new
clang based build.
Fixesgolang/go#10477
Change-Id: I29a179e628466ae0c591620f485194b80e310811
Reviewed-on: https://go-review.googlesource.com/21186
Reviewed-by: David Crawshaw <crawshaw@golang.org>
imWildCat
pushed a commit
to imWildCat/go-mobile
that referenced
this issue
Apr 11, 2021
Now that darwin/arm no longer use an explicit -p=1 in the go command
remove the explicit -p=<num cpus> from gomobile as well.
While we're here, fix the init test templates to reflect the new
clang based build.
Fixesgolang/go#10477
Change-Id: I29a179e628466ae0c591620f485194b80e310811
Reviewed-on: https://go-review.googlesource.com/21186
Reviewed-by: David Crawshaw <crawshaw@golang.org>
We set -p 1 by default for darwin/arm, because it's impossible to run more than one test at a time on the iOS device (each test is packaged as an app for execution).
https://github.com/golang/go/blob/master/src/cmd/go/build.go#L137
As a result, stdlib builds also happen one package at a time on the host, which can be a bit frustrating when you're looking for a compiler error.
Just for this I don't think it's worth complicating the go command to separate the notions of parallelism, but if some other changes happen to its work scheduling, parallel darwin/arm builds would be nice to have.
The text was updated successfully, but these errors were encountered: