Jeff Grafton

@dekkagaijin did you ever start working on this, as suggested in https://github.com/google/go-containerregistry/issues/207#issuecomment-395186149?

I think something may have changed about formatting in go1.15. When I run the tests locally (against go1.15.8): ``` --- FAIL: TestDurationValue (0.00s) --- FAIL: TestDurationValue/in:_3l (0.00s) values_generated_test.go:8971: Error Trace:...

Yeah, https://github.com/golang/go/commit/201cb046b745f8bb00e3d382290190c74ba7b7e1 caused the new failures. Thinking about how to best fix this now...

(one option would be to test only against go1.15+ and update the test cases, especially given that go1.14 is likely going to EOL soon, though I'm not sure if that's...

Every two minutes, though it appeared to be polling more frequently than that.

We haven't had any issues with 1.31.4 using the same settings.

It'd also be good if we could reuse some of the tests for upstream `build_tar` and `pkg_tar`, or at least add some kind of testing.

I haven't asked, but I don't think there's any precedent of having go in core `bazelbuild/bazel`. Maybe if `pkg_tar` were moved into `bazelbuild/rules_pkg`? Or at least we could see about...

@fejta the built-in python one is slooooow

If I use the python implementation and `bazel build //build/release-tars`, then make a change to `CONTRIBUTING.md` and rebuild `//build/release-tars`, it takes 225s just to rebuild `kubernetes-src.tar.gz` and `kubernetes-server-linux-amd64.tar.gz` (with no...