Thanks to visit codestin.com
Credit goes to github.com

Skip to content

compiler: use hash calculation for determining archive staleness #805

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
myitcv wants to merge 12 commits into
base: master
Choose a base branch
from
Open

compiler: use hash calculation for determining archive staleness #805

Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
e807fdb
compiler: use hash calculation for determining staleness
myitcv Apr 23, 2018
e615455
Add --bv flag to test to log verbose build context messages
myitcv Apr 23, 2018
69257f7
Add build tags to the hash
myitcv Apr 23, 2018
f6baa10
More readable version of hash for debug purposes
myitcv Apr 23, 2018
41c38df
Fix file closing
myitcv Apr 23, 2018
d73d4bb
Address feedback from hajimehoshi
myitcv Apr 23, 2018
9c06cba
Refactor to prefer defers for Close
myitcv Apr 23, 2018
82f8b60
Further refactor to use defer for close
myitcv Apr 23, 2018
2e40249
Use better key name for gopherjs binary hash
myitcv Apr 23, 2018
3d5665a
Move compiler hash calc to init phase
myitcv Apr 24, 2018
5c358e3
Remove --bv flag on test
myitcv Apr 24, 2018
1ed4e6a
Add basic test of new hash staleness
myitcv Apr 28, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add --bv flag to test to log verbose build context messages
  • Loading branch information
@myitcv
myitcv committed May 4, 2018
commit e615455f73ba18fdd1ab515ba212c729fad99234
2 changes: 2 additions & 0 deletions tool.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,11 +298,13 @@ func main() {
run := cmdTest.Flags().String("run", "", "Run only those tests and examples matching the regular expression.")
short := cmdTest.Flags().Bool("short", false, "Tell long-running tests to shorten their run time.")
verbose := cmdTest.Flags().BoolP("verbose", "v", false, "Log all tests as they are run. Also print all text from Log and Logf calls even if the test succeeds.")
buildVerbose := cmdTest.Flags().BoolP("bv", "", false, "Use a verbose build context.")
Copy link
Member Author

@myitcv myitcv Apr 23, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not essential to have this... but helps to verify when we get cache misses or not in running tests.

Copy link
Member

@hajimehoshi hajimehoshi Apr 23, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering why we need this besides the existing verbose.

Copy link
Member

@hajimehoshi hajimehoshi Apr 24, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ping

compileOnly := cmdTest.Flags().BoolP("compileonly", "c", false, "Compile the test binary to pkg.test.js but do not run it (where pkg is the last element of the package's import path). The file name can be changed with the -o flag.")
outputFilename := cmdTest.Flags().StringP("output", "o", "", "Compile the test binary to the named file. The test still runs (unless -c is specified).")
cmdTest.Flags().AddFlagSet(compilerFlags)
cmdTest.Run = func(cmd *cobra.Command, args []string) {
options.BuildTags = strings.Fields(tags)
options.Verbose = *buildVerbose
err := func() error {
// Expand import path patterns.
patternContext := gbuild.NewBuildContext("", options.BuildTags)
Expand Down