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
When using a gomote, I often want a tight edit/push/test cycle, but the current behavior of gomote push makes this difficult. Specifically, because gomote push deletes all files from the remote tree that aren't in the local tree, I have to re-run a full make.bash every time I edit something and push, rather than just re-running the one test I care about. In general, deleting these files is clearly the right behavior, so I'm not sure what the answer is. Perhaps it shouldn't delete the build-generated files, such as go/src/runtime/internal/sys/zversion.go and maybe go/src/cmd/cgo/zdefaultcc.go and go/src/go/build/zcgo.go. Or perhaps we need to tweak the build process to be more friendly to cleaning the tree. The VERSION file may also be involved.
It used to ignore certain files to enable such a fast cycle. (that's how I used it) but I never updated it after the build cache changes. Should be an easy fix. Will do.
When using a gomote, I often want a tight edit/push/test cycle, but the current behavior of
gomote push
makes this difficult. Specifically, becausegomote push
deletes all files from the remote tree that aren't in the local tree, I have to re-run a fullmake.bash
every time I edit something and push, rather than just re-running the one test I care about. In general, deleting these files is clearly the right behavior, so I'm not sure what the answer is. Perhaps it shouldn't delete the build-generated files, such asgo/src/runtime/internal/sys/zversion.go
and maybego/src/cmd/cgo/zdefaultcc.go
andgo/src/go/build/zcgo.go
. Or perhaps we need to tweak the build process to be more friendly to cleaning the tree. TheVERSION
file may also be involved./cc @bradfitz
The text was updated successfully, but these errors were encountered: