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
Why changing one file in runtime makes "go test -i" rebuild fmt package (and others). Perhaps I am dreaming, but I don't think "go test -i" used to do that:
# pwd
/root/go/root/src/runtime
# git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
# go test -i -v
runtime
errors
sync/atomic
sync
io
unicode
unicode/utf8
bytes
math
syscall
time
os
strconv
reflect
fmt
sort
flag
strings
path/filepath
io/ioutil
math/cmplx
math/rand
os/exec
regexp/syntax
regexp
runtime/debug
bufio
text/tabwriter
runtime/pprof
testing
net/url
text/template/parse
text/template
# go test -i -v
# touch stack1.go
# go test -i -v
runtime
errors
sync/atomic
sync
io
unicode
unicode/utf8
bytes
math
syscall
time
os
strconv
reflect
fmt
sort
flag
strings
path/filepath
io/ioutil
math/cmplx
math/rand
os/exec
regexp/syntax
regexp
runtime/debug
bufio
text/tabwriter
runtime/pprof
testing
net/url
text/template/parse
text/template
#
Alex
The text was updated successfully, but these errors were encountered:
Did you mean "these packages are imported by the testing package"? But why changing runtime package make testing package out of date and in need of rebuild?
Everything relies on the runtime package, and "go test -i" means installing
everything
needed to test this package, so modifying runtime will cause every package
needed
by the runtime tests to reinstall.
Why changing one file in runtime makes "go test -i" rebuild fmt package (and others). Perhaps I am dreaming, but I don't think "go test -i" used to do that:
Alex
The text was updated successfully, but these errors were encountered: