Closed gfr10598 closed 2 years ago
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
active/active.go | 4 | 88.54% | ||
<!-- | Total: | 4 | --> |
Totals | |
---|---|
Change from base Build 7029: | -0.07% |
Covered Lines: | 3840 |
Relevant Lines: | 5986 |
Ok - my local problem was triggered by upgrading (some months ago) to go116. This version defaults GO111MODULE to "on" instead of "auto", so that triggered complaints that there was no main module, and one should run go mod init etc.
There is a single dependency in etl-gardener on etl/etl/globals.go, so go mod tidy includes etl.
So, this might be the fun bit. The tests include these lines: ./parser/parser_test.go: pipe.Exec("tar", "-C", "testdata", "-xvf", "testdata/pt-files.tar.gz"), ./parser/parser_test.go: pipe.Exec("tar", "-C", "testdata", "-xvf", "testdata/web100-files.tar.gz"), ./parser/parser_test.go: pipe.Exec("tar", "-C", "testdata", "-xvf", "testdata/sidestream-files.tar.gz"), Perhaps go mod tidy is actually looking at these files because they are referenced in the go code.
UPSHOT:
Closing to clean up old PRs. For point 2 - https://github.com/m-lab/etl/issues/1083
When building etl-gardener on darwin, go mod fails because of colons in paths in etl/parser/testdata. This allows go mod to ignore that directory.
This change is![Reviewable](https://reviewable.io/review_button.svg)